VDI error 1010

meklemblmeklembl Posts: 107 Bronze 2
edited July 1, 2010 10:09AM in SQL Backup Previous Versions
I am getting the following error when I attempt to backup and compress a 300GB database across our network.

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, that you have the SQL Server System Administrator server role; and that no other
processes are blocking the backup or restore process; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]

I have not had any issue with this process until I upgraded to 6.4.0.56 but I am not about to say it's strictly a SQLBackup issue.

Thanks,
Larry
Larry M
Cleveland, OH USA
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    SQL Backup generates a log file for each process that it runs. The default folder where the logs are stored is C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\<instance name> on Windows 2003 and older, and C:\ProgramData\Red Gate\SQL Backup\Log\<instance name> for Windows Vista and newer.

    Could you please post the contents of the log file for the backup process that raised VDI error 1010?

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • meklemblmeklembl Posts: 107 Bronze 2
    Command:
    EXECUTE master..sqlbackup '-SQL "BACKUP DATABASE [MasterSearch]
    TO DISK = ''\\SqlRptg\E\Backups\Hercules\<AUTO>.sqb''
    WITH DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 2, THREADCOUNT = 4"'


    Results:

    SQL Backup log file 6.4.0.56

    -SQL "BACKUP DATABASE [MasterSearch]
    TO DISK = '\\SqlRptg\E\Backups\Hercules\<AUTO>.sqb'
    WITH DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 2, THREADCOUNT = 4 "
    ERRORS AND WARNINGS


    6/30/2010 7:20:08 AM: Backing up MasterSearch (full database) to:
    6/30/2010 7:20:08 AM: \\SqlRptg\E\Backups\Hercules\MasterSearch_db_20100630_072008.sqb

    6/30/2010 7:20:08 AM: BACKUP DATABASE [MasterSearch] TO VIRTUAL_DEVICE = 'SQLBACKUP_80455E1A-BCF7-4794-A2AA-5C04A6E414AF', VIRTUAL_DEVICE = 'SQLBACKUP_80455E1A-BCF7-4794-A2AA-5C04A6E414AF01', VIRTUAL_DEVICE = 'SQLBACKUP_80455E1A-BCF7-4794-A2AA-5C04A6E414A
    F02', VIRTUAL_DEVICE = 'SQLBACKUP_80455E1A-BCF7-4794-A2AA-5C04A6E414AF03' WITH BUFFERCOUNT = 24, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (MasterSearch), 6/30/2010 7:20:08 AM', DESCRIPTION = N'Backup on 6/30/2010 7:20:08 AM Server:
    HERCULES Database: MasterSearch', FORMAT

    6/30/2010 7:20:38 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, that you have the SQL Server System Administrator server role; and that no other
    processes are blocking the backup or restore process; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
    6/30/2010 7:21:33 AM: SQL error 3013: BACKUP DATABASE is terminating abnormally.
    6/30/2010 7:21:33 AM: SQL error 3201: Cannot open backup device 'SQLBACKUP_80455E1A-BCF7-4794-A2AA-5C04A6E414AF'. Operating system error 0x80070002(The system cannot find the file specified.).
    6/30/2010 7:21:33 AM:
    6/30/2010 7:21:35 AM: Memory profile
    6/30/2010 7:21:35 AM: Type Maximum Minimum Average Blk count Total
    6/30/2010 7:21:35 AM:
    6/30/2010 7:21:35 AM: Commit 935673856 4096 578550 12469 7213944832
    6/30/2010 7:21:35 AM: Reserve 1241448448 4096 134155 11271 1512067072
    6/30/2010 7:21:35 AM: Free 6872180850688 4096 30618003291 287 8787366944768
    6/30/2010 7:21:35 AM: Private 1241448448 4096 370821 23222 8611209216
    6/30/2010 7:21:35 AM: Mapped 1585152 4096 132683 61 8093696
    6/30/2010 7:21:35 AM: Image 33284096 4096 233498 457 106708992
    6/30/2010 7:21:35 AM:

    PROCESSES COMPLETED SUCCESSFULLY

    6/30/2010 7:21:35 AM: Warning 300: Backup failed. Retry attempt: 1
    6/30/2010 7:21:38 AM: BACKUP DATABASE [MasterSearch] TO VIRTUAL_DEVICE = 'SQLBACKUP_00C3C784-B8AC-4C46-80F9-E1EB1B11EB9E', VIRTUAL_DEVICE = 'SQLBACKUP_00C3C784-B8AC-4C46-80F9-E1EB1B11EB9E01', VIRTUAL_DEVICE = 'SQLBACKUP_00C3C784-B8AC-4C46-80F9-E1EB1B11EB9
    E02', VIRTUAL_DEVICE = 'SQLBACKUP_00C3C784-B8AC-4C46-80F9-E1EB1B11EB9E03' WITH BUFFERCOUNT = 24, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 524288, NAME = N'Database (MasterSearch), 6/30/2010 7:20:08 AM', DESCRIPTION = N'Backup on 6/30/2010 7:20:08 AM Server:

    HERCULES Database: MasterSearch', FORMAT

    6/30/2010 8:23:23 AM: Database size : 202.819 GB
    6/30/2010 8:23:23 AM: Compressed data size: 51.444 GB
    6/30/2010 8:23:23 AM: Compression rate : 74.64%

    6/30/2010 8:23:23 AM: Processed 21431344 pages for database 'MasterSearch', file 'MasterSearch_Data' on file 1.
    6/30/2010 8:23:23 AM: Processed 597904 pages for database 'MasterSearch', file 'DFSearchDetails' on file 1.
    6/30/2010 8:23:23 AM: Processed 380008 pages for database 'MasterSearch', file 'DFTables' on file 1.
    6/30/2010 8:23:23 AM: Processed 1058680 pages for database 'MasterSearch', file 'DFIndexes' on file 1.
    6/30/2010 8:23:23 AM: Processed 4134 pages for database 'MasterSearch', file 'MasterSearch_Log' on file 1.
    6/30/2010 8:23:23 AM: BACKUP DATABASE successfully processed 23472070 pages in 3700.732 seconds (51.958 MB/sec).
    Larry M
    Cleveland, OH USA
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    Thanks for posting the log.

    In short, something was blocking the backup from running between 7:20:08 AM and 7:20:38 AM. SQL Server could only start the backup at 7:21:33 AM. Possible causes:

    - another backup of the same database running at that time
    - overloaded server
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • meklemblmeklembl Posts: 107 Bronze 2
    So "something" stopped the backup, but then it restarted and was successful. Is that correct?
    Larry M
    Cleveland, OH USA
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    So "something" stopped the backup, but then it restarted and was successful. Is that correct?

    Kind of, though I wouldn't put it that way. Something prevented the backup from succeeding the first time round. By design, SQL Backup will then re-attempt the backups a further 4 times until it succeeds.

    What happened in your case was that the blocking event completed at 7:21:33 AM. When SQL Backup then re-attempted the backup at 7:21:38 AM, it succeeded.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
Sign In or Register to comment.