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

SQL Backup 5 Hands

jwilleyjwilley Posts: 23
edited July 22, 2009 10:29PM in SQL Backup Previous Versions
Trying to do a full backup using SQLBackup. DB Size + Log is approx 350GB. 560GB available on the drive I want the backup to go to. Currently doing log shipping using SQL Backup and works fine. The Full backup is set for max compression and I recall when I set up log shipping many months ago, the compressed Full was around 60GB -- so I have plenty of space and permissions are fine, etc. Disabled the tlog backup and started a full backup -- tried 3 times -- killed (had to shut down the SQL Backup service and restart) after 10+ hours each. Found these messages in event log that were written within a few minutes of each of my attempts:

SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=9616. Thread=10992. Client. Instance=. VD=Global\SQLBACKUP_8EAC7446-1A55-4ECB-A197-34E9E5C0C2D9_SQLVDIMemoryName_0.

and

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=9616. Thread=10992. Client. Instance=. VD=Global\SQLBACKUP_8EAC7446-1A55-4ECB-A197-34E9E5C0C2D9_SQLVDIMemoryName_0.

really need to get SQLBackup to work -- what's going wrong??

thx -- john

Comments

  • 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. If 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.

    From what I know, version numbers are as follows for sqlvdi.dll:
    - SQL 2000 starts with 2000.080....(e.g. 2000.080.0760.0 for SQL 2000 SP4
    - SQL 2005 starts with 2000.085... (e.g. 2000.085.1054.0 for SQL 2005 and SQL2005 SP1, 2000.085.1054.2004 for SQL 2005 SP2).

    If you are using SQL 2005, you must use the SQL 2005 versions, and if you are using a 64-bit SQL Server, the 32-bit and 64-bit versions of sqlvdi.dll must match. If you are using SQL 2000, you can use the SQL 2005 libraries.
    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.