ERASEFILES on remote server fails for just 1 DB

• 
  The next time this happens, could you please run
  
  EXEC master..sqbutility 9997
  
  to generate a stack trace file, and send me the file (peter.yeoh@red-gate.com)? This file is named SQBCoreService_<instance name>_bugreport.txt, and is located in 'C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\' on Windows 2003 and older, and 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer.
  
  Thanks.

  petey December 21, 2013 19:17

  - 0 +
• 
  Hi
  
  Another quick thing to check for, if you have an anti-virus application that performs an on-access or real-time check of a file when it is opened to read, edited or being created. This may prevent SQL Backup reading the backup file header and deleting the backup file if it meets the criteria for deletion.
  
  Many Thanks
  Eddie

  Eddie D December 23, 2013 08:57

  - 0 +
• 

  eddie davis wrote:

  Hi
  
  Another quick thing to check for, if you have an anti-virus application that performs an on-access or real-time check of a file when it is opened to read, edited or being created. This may prevent SQL Backup reading the backup file header and deleting the backup file if it meets the criteria for deletion.
  
  Many Thanks
  Eddie

  The odd thing, Eddie, is that of all the database backup being copied, this is the only database experiencing issues, and the UNC location is identical for another database on the same instance. If an Anti-virus tool is interfering, why would it choose just this ONE database's files?

  PDinCA January 07, 2014 14:28

  - 0 +
• 

  petey wrote:

  The next time this happens, could you please run
  
  EXEC master..sqbutility 9997
  
  to generate a stack trace file, and send me the file (peter.yeoh@red-gate.com)? This file is named SQBCoreService_<instance name>_bugreport.txt, and is located in ... 'C:\ProgramData\Red Gate\SQL Backup\Log\' on Windows Vista and newer.

  
  Having found that the latest (2 minutes after execution) had also failed to delete files, I ran the command on my Windows 8.1 laptop. Having searched for the file on both the SQL Cluster and my Laptop, no such file exists.
  
  Please advise.

  PDinCA January 07, 2014 14:40

  - 0 +
• 
  Are you able to manually delete any one of the files listed as being in use, from the primary server, and also from the file server?

  petey January 07, 2014 19:28

  - 0 +
• 
  Only if I restart the SQB Core Service. Restarting appears to release whatever enduring lock the Service retains upon alleged completion of the file transfer.
  
  I only dealt with the remote files as they're the only ones cited in any "Completed with warnings" log messages.

  PDinCA January 07, 2014 21:27

  - 0 +
• 
  Sent another email to ZenDesk in hopes of a response after a three week silence.
  
  Update, please?

  PDinCA January 28, 2014 18:15

  - 0 +
• 
  You mentioned that the backup files of another database copied to the same instance does not experience the same problem. Could you please post the backup command used to back up that database? Just want to compare the options used.
  
  Thanks.

  petey January 29, 2014 02:29

  - 0 +
• 
  Hi Peter,
  
  Bad DB:

  EXECUTE master..sqlbackup '-SQL "BACKUP LOG [CustomerData] TO DISK = ''E:\DB_Backups\<database>\<AUTO>.sqb'' WITH ERASEFILES = 2, ERASEFILES_REMOTE = 15, FILEOPTIONS = 4, CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4, COPYTO = ''\\bk2waspk\sq2waspk_logs'', INIT, THREADCOUNT = 6, VERIFY"'
  

  
  Successful DB on same instance:

  EXECUTE master..sqlbackup '-SQL "BACKUP LOG [DataBaseSecurity] TO DISK = ''E:\DB_Backups\<database>\<AUTO>.sqb'' WITH ERASEFILES = 15, ERASEFILES_REMOTE = 15, FILEOPTIONS = 4, CHECKSUM, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 4, COPYTO = ''\\bk2waspk\sq2waspk_logs'', INIT, THREADCOUNT = 6, VERIFY"'
  

  
  CustomerData (~30MB files, 3 seconds) runs every 15 minutes; DataBaseSecurity (>1MB, > 1 second) every hour.

  PDinCA January 29, 2014 15:06

  - 0 +
• 
  Thanks for posting the details. Noticed nothing significantly different between the 2 set of commands.
  
  We need to get a stack trace of SQL Backup's activities the next time you encounter this error. If you ran
  
  EXEC master..sqbutility 9997
  
  and could not find the SQBCoreService_<instance name>_bugreport.txt file, it may be because the SQL Backup Agent service startup account does not have rights to create the file in that folder. Try granting read/write permissions to the above-mentioned folder to the SQL Backup Agent service startup account.
  
  On Windows Vista and newer, the file is generated in the 'C:\ProgramData\Red Gate\SQL Backup\Log\' folder on the SQL Server server.

  petey January 29, 2014 21:16

  - 0 +
• 
  File posted via email to the 10148 incident.
  
  Thanks, Peter.

  PDinCA January 30, 2014 16:19

  - 0 +

Add comment

Please sign in to leave a comment.