Backups of SQL Databases installed on a Windows x64 Bit Server or restores of Sharepoint Content databases fail
| Article:TECH84350 | | | Created: 2008-01-04 | | | Updated: 2012-12-11 | | | Article URL http://www.symantec.com/docs/TECH84350 |
Problem
Backups of SQL Databases installed on a Windows x64 Bit Server fail saying the databases could not be accessed, or a Sharepoint restore of a Content DB fails with "e00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agent."
Error
Database \master was not found, or could not be accessed.
Database \model was not found, or could not be accessed.
Database \msdb was not found, or could not be accessed.
Database \Northwind was not found, or could not be accessed.
Database \pubs was not found, or could not be accessed.
The Remote Agent Debug Log (see Related Document below for more information) displays the following message:
Cause
When backing up SQL Databases running on an x64 Bit Window 2003 Server, or restoring Sharepoint Content Databases, it can fail with above error if there is a mismatch in the SQLVDI File. The error message is a result of a Virtual Device Interface (VDI) failure on the SQL machine. Backup Exec 10.x and above on use VDI for backups of Microsoft SQL Databases.
Solution
1.Download the "Microsoft SQL Server 2005 Backward Compatibility Components - SQLServer2005_BC_x64.msi" from the followigng link:
Apply just the SQL VDI component. After applying it can be noticed that the x86 and x64 file versions match.
An example below:
C:\Program Files (x86)\Microsoft SQL Server\80\COM [version 2000.85.2312.0 NT INTEL X86]
C:\Program Files\Microsoft SQL Server\80\COM [version 2000.85.2312.0 NT AMD64]
Note: If the files were in use, the setup will request a restart. Please reboot the machine and attempt to run a backup job
Resolution 2:
1.Install the latest available service pack for Microsoft SQL Server.
|
|
Legacy ID
300841
Article URL http://www.symantec.com/docs/TECH84350
Terms of use for this information are found in Legal Notices









Thank you.