Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SQL Backup - Huh?

Created: 21 Jan 2013 | 2 comments
Jayaar's picture

Hi

Netbackup 7.5.0.3

Script created to backup database A, B, C and D

All permissions and such configured and correct.

Backup runs and database A stream complete successful, database B stream completes successful but fails on database stream C. Database stream for D runs and completes successful.

Error for C:

01/21/2013 10:47:18 - connecting

01/21/2013 10:47:18 - connected; connect time: 0:00:00

01/21/2013 10:47:23 - Info dbclient (pid=3692) INF - BACKUP STARTED USING

01/21/2013 10:47:23 - Info dbclient (pid=3692) Microsoft SQL Server 2005 - 9.00.5000.00 (X64)

01/21/2013 10:47:23 - Info dbclient (pid=3692) Dec 10 2010 10:38:40

01/21/2013 10:47:23 - Info dbclient (pid=3692) Copyright (c) 1988-2005 Microsoft Corporation

01/21/2013 10:47:23 - Info dbclient (pid=3692) Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

01/21/2013 10:47:23 - Info dbclient (pid=3692) Batch = C:\Netbackup scripts\C.bch, Op# = 1

01/21/2013 10:47:23 - Info dbclient (pid=3692) INF - Using backup image xxxxxxx.MSSQL7.xxxxxx.db.C.~.7.001of001.20130121104740..C

01/21/2013 10:47:23 - Info dbclient (pid=3692) INF - backup database "C" to VIRTUAL_DEVICE='VNBU0-3692-10204-1358758061' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2

01/21/2013 10:47:23 - Info dbclient (pid=3692) INF - Number of stripes: 1, Number of buffers per stripe 2.

01/21/2013 10:47:23 - Info dbclient (pid=3692) INF - Created VDI object for SQL Server instance <cw006p01>. Connection timeout is <300> seconds.

01/21/2013 10:47:36 - Info bpbrm (pid=2576) xxxxxxx is the host to backup data from

01/21/2013 10:47:36 - Info bpbrm (pid=2576) reading file list from client

01/21/2013 10:47:36 - Info bpbrm (pid=2576) starting bphdb on client

01/21/2013 10:47:39 - Info bphdb (pid=10376) Backup started

01/21/2013 10:52:24 - Info dbclient (pid=3692) ERR - Error in GetConfiguration: 0x80770003.

01/21/2013 10:52:24 - Info dbclient (pid=3692)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.

01/21/2013 10:52:27 - Info dbclient (pid=3692) ERR - Error in VDS->Close: 0x80770004.

01/21/2013 10:52:27 - Info dbclient (pid=3692)     CONTINUATION: - An abort request is preventing anything except termination actions.

01/21/2013 10:52:27 - Info dbclient (pid=3692) INF - OPERATION #1 of batch C:\Netbackup scripts\C.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 306(306) seconds.

01/21/2013 10:52:30 - Info dbclient (pid=3692) INF - Results of executing <C:\Netbackup scripts\C.bch>:

01/21/2013 10:52:30 - Info dbclient (pid=3692) <0> operations succeeded. <1> operations failed.

01/21/2013 10:52:30 - Info dbclient (pid=3692) INF - The following object(s) were not backed up successfully.

01/21/2013 10:52:30 - Info dbclient (pid=3692) INF - C

01/21/2013 10:52:30 - end writing

01/21/2013 10:52:48 - Error bpbrm (pid=2576) from client xxxxxxx: ERR - command failed: none of the requested files were backed up (2)

01/21/2013 10:52:48 - Error bpbrm (pid=2576) from client xxxxxxx: ERR - bphdb exit status = 2: none of the requested files were backed up

01/21/2013 10:52:48 - Info bphdb (pid=10376) done. status: 2: none of the requested files were backed up

none of the requested files were backed up  (2)

Comments 2 CommentsJump to latest comment

RamNagalla's picture

01/21/2013 10:52:24 - Info dbclient (pid=3692) ERR - Error in GetConfiguration: 0x80770003.

01/21/2013 10:52:24 - Info dbclient (pid=3692)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.

01/21/2013 10:52:27 - Info dbclient (pid=3692) ERR - Error in VDS->Close: 0x80770004.

01/21/2013 10:52:27 - Info dbclient (pid=3692)     CONTINUATION: - An abort request is preventing anything except termination actions.

01/21/2013 10:52:27 - Info dbclient (pid=3692) INF - OPERATION #1 of batch C:\Netbackup scripts\C.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 306(306) seconds.

hi,

First I would recommend you to increase the Client read time out  and Client connect time out to 1800 sec or more, most of the cases Data base backup required more client read time out.

even after if you are seeing the backup failurs, please provide the Scritps and the dbclient logs

Jayaar's picture

LOL, that is the first thing I asked the customer to do and still waiting for resonse that it has been done. Will attach logs and scrips if the timeout change did not work.