cancel
Showing results for 
Search instead for 
Did you mean: 

SQL databases no longer backup after recent updates

Last week I upgraded one of our database programs. Since then I have realized there was also an automatic update from MS installec, hotfix 2055 for SQL 2000. I am not sure why that hotfix was installed as I am running SQL 2005, not 2000. I attempted to remove it, however it informed me I would adversly affect 30 other programs so I decided not to go that route quite yet. To make a long story short, BE can no longer backup any of my SQL databases, not just the one I updated.  I get several errors, but the latest is that the database is in use. I can run the backup just fine in the SQL enterprise manager, so it has something to do with BE and SQL working together.

Has anyone seen this in the past week?

Any suggestions where to start?

Thanks,
1 Solution

Accepted Solutions
Accepted Solution!

the mismatch of those 2 DLL's

the mismatch of those 2 DLL's is most likely what is causing the issue.  I would suggest contacting Microsoft to getting both of those files to the latest version.

Backup Exec doesn't do SQL backups the same way that SQL does dumps.  Backup Exec has to use the SQL VDI interface to query SQL and that will send Backup Exec all the data.  When you do a SQL Dump from inside of SQL it does not query SQL VDI, only 3rd party applications use it (as per design from Microsoft).

View solution in original post

6 Replies

What version of Backup Exec

What version of Backup Exec are you running?

What is the error you are getting in the job log for the databases?

Also, on the SQL Server do you see any errors from SQLVDI in the event logs?

Version: 11d Rev. 7170 The

Version: 11d Rev. 7170

The Job Log reads:
Backup- MADISON V-79-57344-33938 -
An error occurred on a query to database Dietz.
V-79-57344-33938 - 0x2000e213 (536928787)
V-79-57344-33938 -
An error occurred on a query to database dietzweb.
V-79-57344-33938 - 0x2000e213 (536928787)
V-79-57344-33938 -
An error occurred on a query to database Hopf.
V-79-57344-33938 - 0x2000e213 (536928787)
There are probably a dozen SQLVDI events in the logs on Feb. 10th, which is when the update occured and another dozen today, but none inbetween then.  The ones from today look like this:

SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(2)The system cannot find the file specified.

. Process=2336. Thread=3016. Server. Instance=SHAREPOINT. VD=Global\model_00__42ae76ee_7e19_4086_885e_202285f9d880__SQLVDIMemoryName_0.

The ones from Feb 10th are a different error code and look more like this:

SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=1520. Thread=5812. Client. Instance=. VD=Global\BACKUP{7f11c116-eb70-4fe7-ac66-b3923aa84304}_SQLVDIMemoryName_0.

They are not all identical errors so if I need to post more of them, please let me know.


What is the version of

What is the version of SQLVDI.DLL on the server? Also is the server x86 or x64?

SQLVDI.DLL in my System32

SQLVDI.DLL in my System32 folder is 2000.80.194.0
In my Program Files\Microsoft SLQ Server\80\COM is 2000.85.2102.0

The server is x86.

Thanks again.
Accepted Solution!

the mismatch of those 2 DLL's

the mismatch of those 2 DLL's is most likely what is causing the issue.  I would suggest contacting Microsoft to getting both of those files to the latest version.

Backup Exec doesn't do SQL backups the same way that SQL does dumps.  Backup Exec has to use the SQL VDI interface to query SQL and that will send Backup Exec all the data.  When you do a SQL Dump from inside of SQL it does not query SQL VDI, only 3rd party applications use it (as per design from Microsoft).

View solution in original post

2000.85.2102.0 is the latest

2000.85.2102.0 is the latest one I can find, but I'll keep looking.
Thanks for the starting point.