VDI Error 1010: Failed to get the configuration from the server because the timeout interval has elapsed

Category: Troubleshooting & error messages
Date: 09 Jun 2009
Product: SQL Backup
When attempting a backup, you may receive the following error:

4/29/2008 8:00:30 AM: VDI error 1010: Failed to get the configuration
from the server because the timeout interval has elapsed. Check that the
SQL Server instance is running and that you have the SQL Server System
Administrator server role; or try increasing the value of the VDITimeout
registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL
Backup\BackupSettingsGlobal\[InstanceName]

4/29/2008 8:00:41 AM: SQL error 3013: BACKUP LOG is terminating
abnormally. 4/29/2008 8:00:41 AM: SQL error 3201: Cannot open backup
device 'SQLBACKUP_BD41D4D4-7A6D-44AC-840F-41123F89E369'. Operating
system error 0x80070002(The system cannot find the file specified.).
4/29/2008 8:00:41 AM:

4/29/2008 8:00:43 AM: Memory profile

4/29/2008 8:00:43 AM: Type Maximum Minimum Average
Blk count Total

4/29/2008 8:00:43 AM: ---------------- ----------- -----------
----------- ----------- -----------

4/29/2008 8:00:43 AM: Commit 1504501760 4096 943944
16423 15502397440

4/29/2008 8:00:43 AM: Reserve 1862205440 4096 148355
15169 2250407936

4/29/2008 8:00:43 AM: Free 6863322480640 4096
45017128981 195 8778340151296

4/29/2008 8:00:43 AM: Private 1862205440 4096 567560
31088 17644335104

4/29/2008 8:00:43 AM: Mapped 1585152 4096 135672
65 8818688

4/29/2008 8:00:43 AM: Image 32063488 4096 226996
439 99651584

4/29/2008 8:00:43 AM:

VDI Error 1010 has many causes, this error is due to the late response from the SQL Server creating a timeout error.

When SQL Backup needs to start a backup, it sends a BACKUP DATABASE or BACKUP LOG ... command to SQL Server. SQL Server in turn needs to tell SQL Backup that it is ready to perform the backup. The default duration that SQL Backup waits for the response is 30 seconds, hence the timeout error as SQL Server responded outside of the 30 second interval.

The delay could be caused by many things e.g. a blocking process such as another backup of the same database, or a CPU intensive task that's running and has tied up the server.

You can increase this timeout interval by creating a VDITimeout Registry Key.

By default the The VDITimeout registry key is not created at install time and cannot be set from the GUI. It needs to be set manually.

To configure the The VDITimeout registry key for 6.4 and above:
Open the registry editor, locate the SQL Backup entries for that SQL Server instance e.g. For both 32-bit and 64-bit machines, HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName] and add a DWORD entry named VDITimeout. Enter the number of seconds that you feel is adequate for SQL Server to respond, in your circumstances. Note that the default format for the value is in hexadecimal.

To configure the The VDITimeout registry key for 6.3 and below:
Open the registry editor, locate the SQL Backup entries for that SQL Server instance e.g. For 32-bit machines, HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName], For 64-bit machines, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]and add a DWORD entry named VDITimeout. Enter the number of seconds that you feel is adequate for SQL Server to respond, in your circumstances. Note that the default format for the value is again in hexadecimal.