May
7
2013

Troubleshooting NetBackup Issues and Error Exit Codes

While working with Symantec NetBackup utility for SQL Server encountered several errors where backups are hanging in middle or failing with absurd error codes, below are some useful references and links which helps in troubleshooting such errors,

 

1. VDI related error:

 

Error message 1

2007-06-18 11:21:00.83 spid820 BackupVirtualDeviceFile::ClearError: failure on backup device ‘VDI_DeviceID‘. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

Error message 2

2007-06-18 11:21:00.83 spid820 Error: 18210, Severity: 16, State: 1.
2007-06-18 11:21:00.83 spid820 BackupMedium::ReportIoError: write failure on backup device ‘VDI_DeviceID‘.
Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)

Error message 3

2007-06-18 11:21:00.87 spid820 Error: 18210, Severity: 16, State: 1.
2007-06-18 11:21:00.87 spid820 BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device ‘VDI_DeviceID.
Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.)

 

If backups are failing with similar VDI errors as mentioned above then issue might be linked to a known Microsoft issue (SQL 2000 and 2005),

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

 

2. SQL jobs randomly failing and locking database:

 

ERR – Error in VxBSACreateObject: 3.
CONTINUATION: – System detected error, operation aborted.
ERR – Error in CPipeServer::CreateAgentMetadata: 6.
CONTINUATION: – The system cannot find the file specified.
ERR – Error in VxBSACreateObject: 6.
CONTINUATION: – The handle used to associate this call with a previous VxBSAInit() call is invalid.

 

Solution is available for 7.5 version, to fix issue apply 7.5.0.4 patch on client and server

Ref. Link:
http://www.symantec.com/connect/forums/sql-jobs-randomly-failing-and-locking-databases-7501

 

3. STATUS CODE: 12 “file open failed” errors:

This error is reported during a database agent backup failures on MS SQL databases. The server could not write the backup failure report because the mssql_backup_failures folder is not available or not created in the master server or client under the following path (UNIX): /usr/openv/netbackup/logs or (WINDOWS):<install_path>\netbackup\logs.

Troubleshooting:
Enable the bprd log file on the master and the dbclient log on the client system.

Resolution:
Make sure that the foldermssql_backup_failures exists in the master server and client in the following path:
Windows:<install_path>\netbackup\logs\mssql_backup_failures
UNIX:/usr/openv/netbackup/logs/mssql_backup_failures
Once this directory has been created, run the database backup again.

 

Ref. Link: http://www.symantec.com/business/support/index?page=content&id=TECH37192

 

 

 

Other Useful Reference:

NetBackup Status Codes: http://www.symantec.com/business/support/index?page=content&id=TECH58686

Download PDF

About the Author: Nitin G

Indian born, trekker, biker, photographer, lover of monsoons. I've been working full time with SQL Server since year 2005 and blogs to post the content aquired during my research on new topics or fixing issues faced by me as a DBA while working in different kind of projects, hope some of my posts may helps others in SQLDBA community. Everything you read on my blog is my own personal opinion and any code is provided "AS-IS" with no warranties!

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 224 other subscribers

Translate this blog!

EnglishFrenchGermanItalianPortugueseRussianSpanish

Calender

September 2019
M T W T F S S
« Nov    
 1
2345678
9101112131415
16171819202122
23242526272829
30  

View Post by Categories

%d bloggers like this: