Video Screencast Help

SQL Backups Failing with Error code 2 after client upgrade to

Created: 24 Feb 2013 • Updated: 24 Feb 2013 | 3 comments
Akshay_Sarawat's picture

We have recently upgraded all the netbackup clients in our production environment to

Since the upgrade SQL backups have been failing with error code 2.  The error as per the job details are pasted below

24/02/2013 1:30:21 PM - Error bpbrm(pid=10184) from client OPDSQLC23: ERR - command failed: unimplemented error code 255 (255)
24/02/2013 1:30:21 PM - Error bpbrm(pid=10184) from client OPDSQLC23: ERR - bphdb exit status = 2: none of the requested files were backed up
24/02/2013 1:30:23 PM - end writing

On the SQL client the windows application logs indicates an error

Faulting application name: dbbackex.exe, version: 7.500.412.916, time stamp: 0x5055e257

Faulting module name: xbsa.dll, version: 7.500.412.916, time stamp: 0x5055dcde

Exception code: 0xc0000005

Fault offset: 0x000000000000d576

Faulting process id: 0x8d4

Faulting application start time: 0x01ce12363db45b8a

Faulting application path: C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe

Faulting module path: C:\Program Files\Veritas\NetBackup\bin\xbsa.dll

Report Id: 8314bf23-7e29-11e2-a9d2-00215a9b1b16


I logged a call with tech support and was told to roll back the upgrades for the time being.

Has anyone come across this error before ? Any assistance would be appreciated.

Operating Systems:

Comments 3 CommentsJump to latest comment

Akshay_Sarawat's picture

Sorry here are the OS details

SQL Client: Windows 2008 R2 SP1

Master Server: Windows 2003 R2 SP2

Media server: Windows 2003 R2 SP2

William Jansen van Nieuwenhuizen's picture

Can you create the dbclient log file and post it?

Also check the machine has enough memory. Is the backup when doing an log backup or when doing a full backup?

To answer your question. I've seen error code 2's with SQL backups when there are VSS issues and memory issues. Most get resolved by rebooting the SQL host.

BTLOMS's picture

log back into the server as the SQL SA account.....configure the backup BCH script once again. It will work.