Warning Deleting Old Files

• 
  Was the file deleted?

  petey April 28, 2005 23:57

  - 0 +
• 
  Does a file with the same name already exist in the folder? Maybe it would help to use the INIT option, which overwrites existing files with the same name, or specifying ERASEFILES_ATSTART to delete the files before running the backup.

  Brian Donahue April 29, 2005 12:03

  - 0 +
• 
  No the file was not deleted. And the file does exist. It's just not getting deleted.

  appwright April 29, 2005 14:20

  - 0 +
• 
  I was looking this over. If the filename is not the same will it not delete the old files. I am using the script posted in this forum to delete all backups. This gives each file a unique name. Could that be the problem?

  appwright April 29, 2005 14:53

  - 0 +
• 
  The file names need not be the same for the ERASEFILES or ERASEFILES_ATSTART options to work. Is it possible that the old file is in use by another application at the time that SQL Backup tries to delete it e.g. virus scanners, batch copy jobs etc?

  petey April 29, 2005 19:49

  - 0 +
• 

  petey wrote:

  The file names need not be the same for the ERASEFILES or ERASEFILES_ATSTART options to work. Is it possible that the old file is in use by another application at the time that SQL Backup tries to delete it e.g. virus scanners, batch copy jobs etc?

  
  Nope - nothing would be touching those files. It happens when I run it from the command line also.

  appwright May 04, 2005 12:03

  - 0 +
• 
  Could you pls list out the file attributes of the backup file that is not being deleted, as displayed in Windows Explorer? Thanks.

  petey May 04, 2005 22:38

  - 0 +
• 
  Attributes? I guess you mean ReadOnly and Hidden. Both are unchecked. File size is 7.02MB, the one that failed today we created on May 03 2005. File name is: TAHOE_DEV2_db_(full)_200505032206.sqb.
  
  Here is the warning on it:
  
  5/5/2005 10:06:31 PM: SQL Backup 3.1.0, (c) Red Gate Software Ltd 2004 - 2005
  5/5/2005 10:06:31 PM:
  5/5/2005 10:06:31 PM: Backing up DEV2 (full database) on TAHOE instance to \Backups\TAHOE_DEV2_db_(full)_200505052206.sqb ...
  5/5/2005 10:06:31 PM:
  5/5/2005 10:06:31 PM: BACKUP DATABASE [DEV2] TO DISK = 'D:\Backups\TAHOE_DEV2_db_(full)_200505052206.sqb' WITH NAME = 'Database (DEV2) Full 200505052206', DESCRIPTION = '', INIT, PASSWORD = 'XXXXXXXXXX', ERASEFILES_ATSTART = 2, MAILTO = 'porter@2morrow.com', COMPRESSION = 3
  5/5/2005 10:06:31 PM:
  5/5/2005 10:06:31 PM: Deleting old backup file: \Backups\TAHOE_DEV2_db_(full)_200505022206.sqb
  5/5/2005 10:06:31 PM: Warning 161: ERASEFILES error: Failed to delete file: \Backups\TAHOE_DEV2_db_(full)_200505022206.sqb. Error code: 158 (The segment is already unlocked).
  5/5/2005 10:06:32 PM: osql -S TAHOE\TAHOE -Q "BACKUP DATABASE [DEV2] TO VIRTUAL_DEVICE = 'SQLBACKUP_207628493' WITH BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = 'Database (DEV2) Full 200505052206', DESCRIPTION = '', FORMAT" -b -w 120 -U sa -P XXXXXXXXXX
  5/5/2005 10:06:35 PM: Backup data size : 25.500 MB
  5/5/2005 10:06:35 PM: Compressed data size: 7.024 MB
  5/5/2005 10:06:35 PM: Compression rate : 72.45%
  5/5/2005 10:06:38 PM: Process completed successfully.
  5/5/2005 10:06:38 PM:

  appwright May 05, 2005 22:32

  - 0 +
• 
  BTW: I'm using the script that was posting in the forum to backup all databases. Is there anything wrong with that script?

  appwright May 05, 2005 22:34

  - 0 +
• 
  Hello Todd,
  
  There are a few more attributes than read-only and hidden. I think that Peter's concerned because there is some code in SQL Backup that checks all of these attributes because you can tell the ERASEFILES option not to erase files with a certain attribute set. I've written a bit of script that can help. If you copy and paste this script into notepad, then save it to a file and run it, it will report all of the attributes set on a file:
  
  cscript fileattrs.js /file:<name of file>
  
  Here is the code:
  

  /* script to list all possible file attributes */
  /* 2005 Brian Donahue Red Gate Software Ltd */
  /* Requires WScript 5.6 (2000/XP)*/
  
  var filename = WScript.Arguments.Named.Item("file");
  
  var FSO = new ActiveXObject("Scripting.FileSystemObject");
  var obFile=FSO.GetFile(filename);
  
  var aNone=0;
  var aReadOnly=1;
  var aHidden=2;
  var aSystem=4;
  var aVolume=8;
  var aDirectory=16;
  var aArchive=32;
  var aAlias=64;
  var aCompressed=128;
  
  var output = "attributes of "+filename +"\r\n";
  if (obFile.Attributes==aNone) output += "There are no attributes set";
  else {
  	if (aReadOnly==(obFile.Attributes & aReadOnly)) output += "Read Only\r\n";
  	if (aHidden==(obFile.Attributes & aHidden)) output += "Hidden\r\n";
  	if (aSystem==(obFile.Attributes & aSystem)) output += "System\r\n";
  	if (aVolume==(obFile.Attributes & aVolume)) output += "Volume\r\n";
  	if (aDirectory==(obFile.Attributes & aDirectory)) output += "Directory\r\n";
  	if (aArchive==(obFile.Attributes & aArchive)) output += "Archive\r\n";
  	if (aAlias==(obFile.Attributes & aAlias)) output += "Alias\r\n";
  	if (aCompressed==(obFile.Attributes & aCompressed)) output += "Compressed\r\n";
  	
  }
  WScript.Echo(output);
  

  Brian Donahue May 06, 2005 10:51

  - 0 +
• 
  Here is the output for that file:
  
  \Backups>cscript fileattrib.js /file:TAHOE_DEV2_db_(full)_200505032206.sqb
  Microsoft (R) Windows Script Host Version 5.6
  Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
  
  attributes of TAHOE_DEV2_db_(full)_200505032206.sqb
  Archive

  appwright May 06, 2005 14:18

  - 0 +
• 
  I have some new information:
  
  I noticed that it is actually deleting older files, however it is saying it is not. Any ideas?

  appwright May 09, 2005 10:18

  - 0 +
• 
  I have encountered the same situation where the files are deleted but the warning you described is raised, due to a quirk in the file deleting function that's used. That was why my original response to your issue was to check if the file(s) were actually deleted.
  
  In 3.2, a check is actually made if the physical file exists, before a warning is raised.

  petey May 09, 2005 12:24

  - 0 +
• 
  Can I get 3.2?
  
  I also noticed that even if I have the deletion set for 1, I will still end up with 2 files in holding instead of just the current backup.

  appwright May 09, 2005 13:58

  - 0 +
• 
  >> I also noticed that even if I have the deletion set for 1, I will still end up with 2 files in holding instead of just the current backup.
  
  Check the timestamp of the two files. SQB will only delete the older file if it is >= 24 hours older than the timestamp of the current backup file.

  petey May 10, 2005 04:24

  - 0 +
• 
  The new version 3.2 has solved the Warning problem. No more file delete warnings!

  appwright May 10, 2005 22:11

  - 0 +

Add comment

Please sign in to leave a comment.