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

SQL Backup failed on vdi error

gsc_ghxgsc_ghx Posts: 73
edited March 10, 2008 3:29AM in SQL Backup Previous Versions
I have a backup that has failed now for several nights. This morning the error was reported as:
SQL Backup log file
3/9/2008 5:01:18 AM: Backing up CAT_Broward (full database) to:
\\prdsmb1\sqlbkp\CATSQL02\CAT_Broward_FULL_RG.bak

3/9/2008 5:01:18 AM: BACKUP DATABASE [CAT_Broward] TO DISK = '\\prdsmb1\sqlbkp\CATSQL02\CAT_Broward_FULL_RG.bak' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, COMPRESSION = 1

3/9/2008 5:01:33 AM: 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.)
3/9/2008 5:03:10 AM: SQL error 3013: BACKUP DATABASE is terminating abnormally.
3/9/2008 5:03:10 AM:
3/9/2008 5:03:10 AM: Memory profile

3/9/2008 5:03:10 AM: Type Maximum Minimum Average Blk count Total
3/9/2008 5:03:10 AM:





3/9/2008 5:03:10 AM: Commit 66519040 4096 34513 28253 975114240
3/9/2008 5:03:10 AM: Reserve 3411968 4096 65760 26945 1771905024
3/9/2008 5:03:10 AM: Free 460832768 4096 2634114 180 474140672
3/9/2008 5:03:10 AM: Private 66519040 4096 0 54609 -1611689984
3/9/2008 5:03:10 AM: Mapped 1536000 4096 144935 65 9420800
3/9/2008 5:03:10 AM: Image 7581696 4096 103666 524 54321152
3/9/2008 5:03:10 AM:
3/9/2008 5:03:10 AM:
3/9/2008 5:03:10 AM: Warning 300: Backup failed. Retry attempt: 1
3/9/2008 5:03:12 AM: BACKUP DATABASE [CAT_Broward] TO DISK = '\\prdsmb1\sqlbkp\CATSQL02\CAT_Broward_FULL_RG.bak' WITH NAME = 'Database (CAT_Broward), 3/9/2008 5:01:18 AM', DESCRIPTION = 'Backup on 3/9/2008 5:01:18 AM Server: CATSQL02 Database: CAT_Broward', INIT, COMPRESSION = 1

3/9/2008 5:05:18 AM: Backup data size : 4.317 GB
3/9/2008 5:05:18 AM: Compressed data size: 514.818 MB
3/9/2008 5:05:18 AM: Compression rate : 88.35%

Processed 506632 pages for database 'CAT_Broward', file 'PRIMARY_01' on file 1.
Processed 58992 pages for database 'CAT_Broward', file 'INDEXES_01' on file 1.
Processed 131 pages for database 'CAT_Broward', file 'LOG_01' on file 1.
BACKUP DATABASE successfully processed 565755 pages in 124.607 seconds (37.194 MB/sec).


From the last of the log it looks like the backup was completed on the second try. Can someone help decipher this error for me?

Thanks
g

Comments

  • Options
    peteypetey Posts: 2,358 New member
    SQL Backup attempted the backup at 3/9/2008 5:01:33 AM. 15 seconds later, at 3/9/2008 5:01:33 AM, it reported that SQL Server could not service the backup request. 1.5 minutes later, SQL Server reported that it could then service the backup request, but could not find the SQL Backup device to back up to.

    This situation can occur due to a number of reasons, the 2 most common being:

    - a process that was running blocked the backup from being performed e.g. another backup of the same database, defragmentation operations etc

    - SQL Server was tied up performing CPU/IO intensive tasks at that time, and could not service the backup request within 15 seconds of the SQL Backup request

    Whatever the reason, SQL Backup will automatically reattempt the backup 4 times. If the backup succeeds on any of the re-attempts, it will report a warning (300), which is only to alert you to the fact that something may be blocking the backups then. It will report an error only if all the backup attempts fail.

    In version 5, the SQL Backup wait interval was increased from 15 seconds to 30 seconds. In version 5.3, the wait interval is user-definable.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.