Home | Site Map | Cisco How To Net How To | Wireless | Search | Forums | Services | Setup Guide | Chicagotech MVP | About Us | Contact Us|

 

Can't backup SQL Database using Barracuda backup

Barracuda ERROR: Failed to open object on data source

Event ID 1, 3201 and 3041

Situation: 1. Barracuda backup log these errors: "SQL: SQLConnect failed for SQL instance [LocalServer]", "SQL: Dump database cmd failed: [4294967295]", "SQL: STATE - [4] Native error: [3201] Message: [[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'deviceADD239F5'. Operating system error 0x80070005(Access is denied.).]", "SQL: STATE - [4] Native error: [3013] Message: [[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.]", "SQL: SQL command failed before VD transfer", "SQL: SQL command failed before VD transfer".

2. The Windows Event Viewer has these logs:

Log Name: Application
Source: SQLVDI
Event ID: 1
Description:
SQLVDI: Loc=SVDS::Open. Desc=OpenProcess. ErrorCode=(5)Access is denied.
. Process=13100. Thread=7488. Server. Instance=MSSQLSERVER. VD=Global\deviceADD239F5.

Log Name: System
Source: VDS Basic Provider
Event ID: 1
Description:
Unexpected failure. Error code: 490@01010004

Log Name: Application
Source: MSSQLSERVER
Event ID: 3201
Description:
Cannot open backup device 'deviceADD239F5'. Operating system error 0x80070005(Access is denied.).

Log Name: Application
Source: MSSQLSERVER
Event ID: 3041
Description:
BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.

3. The client receive this message from their Barracuda backup: **WARNING** The data listed below is not currently accessible by your Barracuda Backup Server and was not backed up as a result.

ERROR: Failed to open object '\Microsoft SQL Server\LocalServer\PEOLive' on data source 'peo'.

Resolution: 1. Register SQLVDI.dll by following these steps:

1)  Stop all of the SQL Services.
2) Launch Windows Explore, search for, and document the location of each instance of sqlvdi.dll.
3) Click Start, click Run, type Regsvr32 Path\SQLVDI.DLL in the Open box, and then click OK.
4)Restart the SQL Server.                

2. Try Microsoft hotfix: FIX: Error messages and an event may be logged when you use the Virtual Device Interface in SQL Server 2005 or in SQL Server 2000

3. This issue is resolved by applying the following update to the SQL Server from Microsoft.

Microsoft SQL Server 2005 Backward Compatibility Components
http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Note: a reboot may be required after the update has been installed.

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

 

 

 

 

  This web is provided "AS IS" with no warranties.
Copyright 2002-2017 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.