errors running SQL backups

Eric_ODell · ‎07-17-2012

I'm getting the following errors when trying to do a sql backup in Netbackup 7.5

7/17/2012 2:49:30 PM - Info nbjm(pid=9788) starting backup job (jobid=11235) for client okcmsqlp04, policy VMware_vCenter, schedule Full

7/17/2012 2:49:30 PM - Info nbjm(pid=9788) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=11235, request id:{966B844B-FA5E-42E3-A92A-29EC97389E5C})

7/17/2012 2:49:30 PM - requesting resource Disk_Backups

7/17/2012 2:49:30 PM - requesting resource okcnbkp02.loves.com.NBU_CLIENT.MAXJOBS.okcmsqlp04

7/17/2012 2:49:30 PM - requesting resource okcnbkp02.loves.com.NBU_POLICY.MAXJOBS.VMware_vCenter

7/17/2012 2:49:30 PM - granted resource okcnbkp02.loves.com.NBU_CLIENT.MAXJOBS.okcmsqlp04

7/17/2012 2:49:30 PM - granted resource okcnbkp02.loves.com.NBU_POLICY.MAXJOBS.VMware_vCenter

7/17/2012 2:49:30 PM - granted resource Backups3

7/17/2012 2:49:30 PM - estimated 0 Kbytes needed

7/17/2012 2:49:30 PM - Info nbjm(pid=9788) started backup (backupid=okcmsqlp04_1342554570) job for client okcmsqlp04, policy VMware_vCenter, schedule Full on storage unit Backups3

7/17/2012 2:49:30 PM - started process bpbrm (2000)

7/17/2012 2:49:32 PM - Info bpbrm(pid=2000) okcmsqlp04 is the host to backup data from

7/17/2012 2:49:32 PM - Info bpbrm(pid=2000) reading file list from client

7/17/2012 2:49:32 PM - connecting

7/17/2012 2:49:34 PM - Info bpbrm(pid=2000) starting bphdb on client

7/17/2012 2:49:34 PM - connected; connect time: 00:00:02

7/17/2012 2:49:35 PM - Info bphdb(pid=6340) Backup started

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) INF - BACKUP STARTED USING

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) Microsoft SQL Server 2005 - 9.00.3080.00 (X64)

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) Sep 6 2009 09:15:46

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) Standard Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) Batch = VMware_vCenter1.bch, Op# = 1

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) INF - Using backup image okcmsqlp04.MSSQL7.OKCMSQLP04.db.VMware_vCenter.~.7.001of001.20120717144936..C

7/17/2012 2:49:37 PM - Info dbclient(pid=4100) INF - backup database "VMware_vCenter" to VIRTUAL_DEVICE='VNBU0-4100-5672-1342554578' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2

7/17/2012 2:49:38 PM - Info dbclient(pid=4100) INF - Number of stripes: 1, Number of buffers per stripe 2.

7/17/2012 2:49:38 PM - Info dbclient(pid=4100) INF - Created VDI object for SQL Server instance <okcmsqlp04>. Connection timeout is <300> seconds.

7/17/2012 2:54:40 PM - Info dbclient(pid=4100) ERR - Error in GetConfiguration: 0x80770003.

7/17/2012 2:54:40 PM - Info dbclient(pid=4100) CONTINUATION: - The api was waiting and the timeout interval had elapsed.

7/17/2012 2:54:45 PM - Info dbclient(pid=4100) ERR - Error in VDS->Close: 0x80770004.

7/17/2012 2:54:45 PM - Info dbclient(pid=4100) CONTINUATION: - An abort request is preventing anything except termination actions.

7/17/2012 2:54:45 PM - Info dbclient(pid=4100) INF - OPERATION #1 of batch VMware_vCenter1.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 309(309) seconds.

7/17/2012 2:54:47 PM - Info dbclient(pid=4100) INF - Results of executing <VMware_vCenter1.bch>:

7/17/2012 2:54:47 PM - Info dbclient(pid=4100) <0> operations succeeded. <1> operations failed.

7/17/2012 2:54:47 PM - Info dbclient(pid=4100) INF - The following object(s) were not backed up successfully.

7/17/2012 2:54:47 PM - Info dbclient(pid=4100) INF - VMware_vCenter

7/17/2012 2:54:47 PM - Error bpbrm(pid=2000) from client okcmsqlp04: ERR - command failed: none of the requested files were backed up (2)

7/17/2012 2:54:47 PM - Error bpbrm(pid=2000) from client okcmsqlp04: ERR - bphdb exit status = 2: none of the requested files were backed up

7/17/2012 2:54:48 PM - Error bpbrm(pid=2000) cannot send mail to eric.odell@loves.com,chris.chasteen@loves.com

7/17/2012 2:54:49 PM - end writing

none of the requested files were backed up(2)

Where am I going wrong?

Will_Restore · ‎07-18-2012

Connection timeout is <300> seconds.

Elapsed time = 309(309) seconds

The timeout problem can be resolved by increasing the NetBackup Client Read

Timeout setting. Use the NetBackup Administration Console on the server to

change the properties of each client that contains a database you may need to

restore. The default for the Client Read Timeout setting is 300 seconds (5 minutes).

If you have any clients which contain large SQL Server databases, you may need

to set this value much higher.

try 1800 seconds

Eric_ODell · ‎07-18-2012

In NetBackup I have the timeout set to 9600 seconds, but it doesn't seem to represnt that. 300 seconds or 309 was suprising to me as well. Is there somewhere in the script to change this value?

Will_Restore · ‎07-18-2012

that extract from the guide implies setting on the client server

reset Client Read Timeout on the Master Server and any Media Server as well

Eric_ODell · ‎07-18-2012

I have the setting for the client time out at 9600 seconds

Will_Restore · ‎07-18-2012

If you reset Client Read Timeout on all the machines and it still says 300 seconds in the log, restart NetBackup services. Been a long time since I did it but I think it was the Media Server reset that did the trick.

VOX

errors running SQL backups