Backup only succeeds after retry

• 
  Yes, this issue should be resolved by specifying a MAXTRANSFERSIZE parameter in the backup job.
  
  With v5 you are now able to specify the MAXTRANSFERSIZE parameter while setting up a job. You can choose from the largest of 1024kb right down to 64kb, so it should be easy to fix if you ever get these warnings again.

  Chris Auckland May 10, 2007 23:24

  - 0 +
• 
  I'm experiencing the same problem, also running SQL Backup 4.6.0.815. I have already specified a value for MAXTRANSFERSIZE of 262144 but the problem persists
  

  20/09/2007 20:00:05: BACKUP LOG [Aries_Test]  TO DISK = 'E:\Aries_Test\LOG_(local)_Aries_Test_20070920_200005.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 7, MAILTO_ONERROR = 'dbu@bl.uk', COMPRESSION = 3, THREADS = 1
  
  20/09/2007 20:00:05: Deleting old backup file: E:\Aries_Test\LOG_(local)_Aries_Test_20070912_200006.sqb
  20/09/2007 20:00:20: VDI error 1010: Failed to get configuration from server.  Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role.  Error code:  (-2139684861: The api was waiting and the timeout interval had elapsed.)
  20/09/2007 21:26:42: SQL error 3013: BACKUP LOG is terminating abnormally.
  20/09/2007 21:26:42: 
  20/09/2007 21:26:43: Memory profile
  20/09/2007 21:26:43: Type             Maximum     Minimum     Average     Blk count   Total      
  20/09/2007 21:26:43: ---------------- ----------- ----------- ----------- ----------- -----------
  20/09/2007 21:26:43: Commit           840499200   4096        1356706     1276        1731158016 
  20/09/2007 21:26:43: Reserve          27328512    4096        801007      197         157798400  
  20/09/2007 21:26:43: Free             163753984   4096        1353202     191         258461696  
  20/09/2007 21:26:43: Private          840499200   4096        2034763     898         1827217408 
  20/09/2007 21:26:43: Mapped           1536000     4096        178211      57          10158080   
  20/09/2007 21:26:43: Image            7569408     4096        99577       518         51580928   
  20/09/2007 21:26:43: 
  20/09/2007 21:26:43: Warning 300: Backup failed.  Retry attempt: 1
  20/09/2007 21:26:45: BACKUP LOG [Aries_Test]  TO DISK = 'E:\Aries_Test\LOG_(local)_Aries_Test_20070920_200005.sqb' WITH NAME = 'Database (Aries_Test), 20/09/2007 20:00:05', DESCRIPTION = 'Backup on 20/09/2007 20:00:05  Server: [myServer] Database: Aries_Test', INIT, ERASEFILES_ATSTART = 7, COMPRESSION = 3, THREADS = 1
  
  20/09/2007 21:26:45: Deleting old backup file: E:\Aries_Test\LOG_(local)_Aries_Test_20070913_200006.sqb
  20/09/2007 21:26:45: Backup data size    : 640.000 KB
  20/09/2007 21:26:45: Compressed data size: 7.000 KB
  20/09/2007 21:26:45: Compression rate    : 98.91%
  
  Processed 1 pages for database 'Aries_Test', file 'TPM_Log' on file 1.
  BACKUP LOG successfully processed 1 pages in 0.005 seconds (0.512 MB/sec).
  --------------------------------------------------------------------------------
  

  sidownes September 21, 2007 05:04

  - 0 +
• 
  In your case it looks like it succeeded on the second attempt. You may find that if the step down the MAXTRANSFERSIZE parameter to 131072 you will no longer receive the warnings.
  
  I hope this helps.

  Chris Auckland September 24, 2007 00:31

  - 0 +
• 
  No good, still same problem of it only working intermittently on first attempt. Parameters set to MAXDATABLOCK = 131072 and
  MAXTRANSFERSIZE = 65536

  sidownes October 17, 2007 08:59

  - 0 +
• 
  bump

  sidownes October 29, 2007 10:52

  - 0 +
• 
  Sorry about this delay. I must have missed your last update.
  
  Here is a link to a knowledgebase article that lists some common solutions to this issue.
  http://www.red-gate.com/support/kb/KB200710000177.htm
  
  If the server has also been running for a long time, and under somewhat heavy load, I think it would be a good idea to restart the SQL Server service if possible. This shouldn't really be necessary with modern versions of SQL Server, but it has been known to resolve these issues in the past.
  
  Have you tried SQL Backup 5? There have been some improvements to the way that the SQL backup task is retried if the SQL Server is low on contiguous memory. This may also fix the problem for you.

  Chris Auckland October 29, 2007 16:25

  - 0 +

Add comment

Please sign in to leave a comment.