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

SQLBackup 5.4 - Backup and Restore Failed

GladiatrGladiatr Posts: 28
edited November 28, 2008 4:35PM in SQL Backup Previous Versions
Hi guys,

I need some help on this issue.

We have W2K8SP1 Enterprise x64bit w/ SQL 2005 SP2 standard running on 16GB. When I try to restore the database from the backup I get this:

TEST: Restore - Failed

Restoring full backup - Failed

This operation failed with errors.

Restoring EQSite (database) from:
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]
Also check that the database is not currently in use.
SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 3201: Cannot open backup device 'SQLBACKUP_997576AB-F6A5-4BEE-9881-393958967C87'. Operating system error 0x80770006(error not found).
Memory profile
Type Maximum Minimum Average Blk count Total

Commit 3997696000 4096 3316879 1335 4428034048
Reserve 13186826240 16384 150519575 88 13245722624
Free 6863322480640 4096 41213235680 213 8778419200000
Private 13186826240 4096 22984841 761 17491464192
Mapped 3866624 4096 773056 113 87355392
Image 32063488 4096 172927 549 94937088
SQL Backup exit code: 1010
SQL error code: 3201

Updating SQL Server information - Pending

Operation pending.

Can anyone please able to help me and resolve this issue. This is a kind of urgent as we are moving our production databases to this environment which will be our future production server.



  • Options
    peteypetey Posts: 2,358 New member
    I would check the sqlvdi.dll versions.

    In the registry, look for the key {40700425-0080-11d2-851f-00c04fc21759} in HKEY_CLASSES_ROOT. In the subkey InprocServer32, look for the copy of sqlvdi.dll that is used. Check the version number of this file. Since you are running a 64-bit system, you should find another entry in HKEY_CLASSES_ROOT\Wow6432Node\CLSID. Again, check the version number of this file and ensure it matches the 64-bit copy.

    The 32-bit and 64-bit versions of sqlvdi.dll must match.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Thanks Petey for the prompt reply.

    I did check as you mentioned the sqlvdi.dll version and I found four copies at the following locations and there version numbers are stated in brackets:

    C:\Program Files\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2102.0)
    C:\Program Files\Microsoft SQL Server\80\Tools\sqlvdi.dll (2000.85.2102.0)
    C:\Program Files (x86)\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2004.0)
    C:\Program Files (x86)\Microsoft SQL Server\80\Tools\sqlvdi.dll (2000.85.2004.0)

    So, as you said in your reply I matched the entry in HKEY_CLASSES_ROOT\Wow6432Node\CLSID to the 64-bit copy.

    Now, my 32bit and 64bit are using C:\Program Files\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2102.0), but now I'm getting VDI error 1030.

    Do I have to use this file C:\Program Files (x86)\Microsoft SQL Server\80\sqlvdi.dll (2000.85.2004.0) instead which looks more updated to me but its in the 32bit program files folder.

    Any thought on this?

    This is a bit urgent now because we have plans for this coming Saturday to use this box as our new productions server.

    Any help on this will be appreciated.

  • Options
    peteypetey Posts: 2,358 New member
    The 32-bit registered version must be a 32-bit file, and the 64-bit registered version must be a 64-bit file. Hence, you cannot point both entries in the registry to the same file. I think that you have pointed both entries to the 64-bit version (C:\Program Files\Microsoft SQL Server\80\sqlvdi.dll).

    On your system, it looks like there isn't a 32-bit version of sqlvdi.dll version 2000.85.2102.0. You can get a copy from this hotfix: http://support.microsoft.com/kb/934396. It should install and register the file for you.

    2000.85.2004.0 is the version that's installed with SQL Server 2005 SP2. 2000.85.2102.0 was either installed with the above hotfix, or in a cumulative update. For some reason, only the 64-bit files were updated, but not the 32-bit files.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Hi Petey,

    Once again thank you so much for your prompt reply and in fact you have also saved my day as well. I guess, I must have misunderstood what you said in your first reply to my query.

    Anyhow, I download the hot fix throught the link that you had sent to me on my x64 box and installed it and problem seems to be fixed now as this time I'm able to take the backup of my databases through the SQLBackup 5.4 GUI and as well through the MS SQL Management Studio. Before that, I was unable to take the backup or verify the databases.

    May be what I did wrong could be this that on my x64 box I must have installed the SQL Backward Compatibility pack for 32bit instead of 64bit. This might have caused this problem.

    But once again thank you for your support.

Sign In or Register to comment.