What are the challenges you face when working across database platforms? Take the survey

Failed backup errors

ToehoToeho Posts: 73
edited October 3, 2007 11:25AM in SQL Backup Previous Versions
We are getting the following error on one of our databases when we take a full backup, all other databases will backup successfully. Can you please provide some insite on what the error relates too???

Backing up PRD (full database) to:

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: (-2139684860: An abort request is preventing anything except
termination actions.)
SQL error 3013: BACKUP DATABASE is terminating abnormally.

Memory profile
Type Maximum Minimum Average Blk count Total

Commit 1072431104 4096 2110933 1366 2883534848
Reserve 4128768 4096 402206 200 80441344
Free 33488896 4096 1054031 244 257183744
Private 1072431104 4096 2727573 1074 2929414144
Mapped 1019904 4096 124440 42 5226496
Image 7569408 4096 65190 450 29335552

Warning 300: Backup failed. Retry attempt: 1

Warning 300: Backup failed. Retry attempt: 2

Warning 300: Backup failed. Retry attempt: 3

Warning 300: Backup failed. Retry attempt: 4

SQL Backup exit code: 1010
SQL error code: 3013
name value

exitcode 1010
sqlerrorcode 3013
filename001 h:\Backups\PRD_10022007_210008_FULL_01.sqb
filename002 h:\Backups\PRD_10022007_210008_FULL_02.sqb
filename003 h:\Backups\PRD_10022007_210008_FULL_03.sqb
filename004 h:\Backups\PRD_10022007_210008_FULL_04.sqb
filename005 h:\Backups\PRD_10022007_210008_FULL_05.sqb
filename006 h:\Backups\PRD_10022007_210008_FULL_06.sqb
filename007 h:\Backups\PRD_10022007_210008_FULL_07.sqb
filename008 h:\Backups\PRD_10022007_210008_FULL_08.sqb
SQL Backup v5.1.0.2781


  • Options
    The key issue seems to be with the amount of contiguous free memory available, 33.4MB (33,488,896 bytes) is the largest block according to the "Memory Profile".

    When performing a backup with 8 files, SQL Backup will attempt to use 33.5MB of contiguous memory to perform the backup, which is not currently available.

    This means that SQL Backup should attempt to perform a backup with a smaller value of MAXTRANSFERSIZE (half the previous/default value), however there was a bug in 5.0 and 5.1 where this retry would not happen, causing the backup to fail after trying one backup.

    There are three options available here:

    * The first is to restart the SQL Server process, which will clear up any of the fragmentation that has been caused in the memory space.

    * The second would be to upgrade to 5.2, which will retry the backup if the amount of contiguous memory is too small. This means that the above situation would succeed (since it can perform the backup with 16.8MB of memory), but as the fragmentation continues a restart of the SQL Server process may be required.

    * The third, still using SQL Backup 5.1, would be to manually use a smaller value of MAXTRANSFERSIZE, or use a smaller number of files. This will reduce the contiguous memory required to perform the backup. However this will also eventually hit the same problems as described in the second option.

    More information on this issue is provided in the following Knowledge Base article: http://www.red-gate.com/Support/kb/KB200708000117.htm

    Hope that helps,
Sign In or Register to comment.