Sporadic VDI error 1010

charleyevans

Hello,

This error occurs sporadically on our SQL 2005 EE x64 server.

"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.)"

Here is the log for one of these occurrences.

2/7/2007 7:30:03 AM: Backing up Legal_Advantage_Dev (transaction log) to:
\\192.168.100.27\SQLBackup\LOG_(local)_Legal_Advantage_Dev_20070207_073003.sqb

2/7/2007 7:30:03 AM: BACKUP LOG [Legal_Advantage_Dev] TO DISK = '\\192.168.100.27\SQLBackup\LOG_(local)_Legal_Advantage_Dev_20070207_073003.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES = 1h, COMPRESSION = 3, THREADS = 1

2/7/2007 7:30:18 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.)
2/7/2007 7:30:26 AM: SQL error 3013: BACKUP LOG is terminating abnormally.
2/7/2007 7:30:26 AM: SQL error 3201: Cannot open backup device 'SQLBACKUP_BD79D538-2736-4CAF-823E-E97A446306D2'. Operating system error 0x80070002(The system cannot find the file specified.).
2/7/2007 7:30:26 AM:
2/7/2007 7:30:30 AM: Memory profile
2/7/2007 7:30:30 AM: Type Maximum Minimum Average Blk count Total
2/7/2007 7:30:30 AM:

---

---

---

---

---

---

2/7/2007 7:30:30 AM: Commit 828276736 4096 676727 11364 7690326016
2/7/2007 7:30:30 AM: Reserve 1224671232 4096 790978 9793 7746056192
2/7/2007 7:30:30 AM: Free 6864836558848 4096 37847657648 232 8780656574464
2/7/2007 7:30:30 AM: Private 1224671232 4096 755271 20206 15261016064
2/7/2007 7:30:30 AM: Mapped 3948544 4096 171870 76 13062144
2/7/2007 7:30:30 AM: Image 32976896 4096 185490 875 162304000
2/7/2007 7:30:30 AM:
2/7/2007 7:30:30 AM: Warning 300: Backup failed. Retry attempt: 1
2/7/2007 7:30:32 AM: BACKUP LOG [Legal_Advantage_Dev] TO DISK = '\\192.168.100.27\SQLBackup\LOG_(local)_Legal_Advantage_Dev_20070207_073003.sqb' WITH NAME = 'Database (Legal_Advantage_Dev), 2/7/2007 7:30:03 AM', DESCRIPTION = 'Backup on 2/7/2007 7:30:03 AM Server: 107523-DB1 Database: Legal_Advantage_Dev', INIT, ERASEFILES = 1h, COMPRESSION = 3, THREADS = 1

2/7/2007 7:31:47 AM: Backup data size : 1,009.188 MB
2/7/2007 7:31:47 AM: Compressed data size: 305.424 MB
2/7/2007 7:31:47 AM: Compression rate : 69.74%

Processed 129066 pages for database 'Legal_Advantage_Dev', file 'Legal_Advantage_Dev_log' on file 1.
BACKUP LOG successfully processed 129066 pages in 75.369 seconds (14.028 MB/sec).

---

2/7/2007 7:31:59 AM: Deleting old backup file: \\192.168.100.27\SQLBackup\LOG_(local)_Legal_Advantage_Dev_20070207_063003.sqb

As you see, the backup succeeds on the first retry. I don't see any problem with the amount of memory available (perhaps I am reading the log incorrectly). We shouldn't have any processor problems as well as we are 2 X dual core procs. Might this error be caused by other resource contention such as I/O?

petey

Is there a possibility that the server was busy during that time?

The backup was started at 7:30:03. SQL Backup will connect to SQL Server and issue a BACKUP command internally. The timeout is 15 seconds, which is 7:30:18. At this point, SQL Backup aborts the process, but it needs to wait for the connection to SQL Server to close. This connection was closed at 7:30:26, and the error indicates that the BACKUP command was received, but SQL Server was unable to connect to the SQL Backup endpoint. The connection was likely only established between 7:30:18 (after SQL Backup had closed its endpoint) and 7:30:26.