Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

MS SQL Server backup quits with Status Code 1

Updated: 21 May 2010 | 1 comment
Mohannbu's picture
0 0 Votes
Login to vote
Dear Team,

NetBackup Version - 6.5.1
Master Server          - HPUX.B.11.11.
Media Server           - HPUX.B.11.11
Client                         - WindowsNET  - LCCDB056
Client                        -  Windows2003 - UCCNETP

MSSQl backup's which is listed below has completed partially successful. We've re-run the backup it has completed successfully. But, I need to know the root cause for this failure. Kindly help me out to know the root cause of this issue. It seems like communication issue, I need to know how and why?

Veritas Error log details for UCCNETP Instance as on Saturday, November 14th Night)

========================================================================================
 
INF - Created VDI object for SQL Server instance <UCCNETP>. Connection timeout is <300> seconds.
20:35:27.566 [5396.5300] <4> : 20:35:21 INF - Server status = 25
ERR - Error in VxBSACreateObject: 3.
    CONTINUATION: - System detected error, operation aborted.
ERR - Error in GetCommand: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
ERR - Error in VDS->Close: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #3 of batch D:\program files\veritas\awi\scripts\uccnetp_full_online_database_backup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 330(330) seconds.

Error log from the Veritas admin console for UCCNETP
============================================
This error occured in one of the agent backup,

11/14/2009 8:32:51 PM - connecting
11/14/2009 8:33:52 PM - Error bpbrm(pid=23296) cannot connect to lccdb112p1, No such file or directory (2)  
11/14/2009 8:33:52 PM - Error bpbrm(pid=23296) listen for client protocol error - couldn't write necessary information on /D/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/5300.0.1258248697
11/14/2009 8:33:53 PM - end writing
cannot connect on socket(25)

 
Veritas Error log details for LCCDB056\Default Instance as on Saturday, November 14th Night)
==================================================================================================
 
20:16:35.683 [5812.5248] <4> : 20:16:28 INF - Server status = 25
ERR - Error in VxBSACreateObject: 3.
    CONTINUATION: - System detected error, operation aborted.
ERR - Error in VDS->Close: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #6 of batch D:\Program Files\VERITAS\awi\scripts\lccdb056_full_online_database_backup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 327(0) seconds.
INF - BACKUP STARTED USING

Error log from the Veritas admin console for LCCDB056\Default
===================================================

This error occured in one of the agent backup,

11/14/2009 8:12:08 PM - connecting
11/14/2009 8:14:20 PM - Error bpbrm(pid=22845) cannot connect to lccdb056p1, Interrupted system call (4)    
11/14/2009 8:14:21 PM - Error bpbrm(pid=22845) listen for client protocol error - couldn't write necessary information on /D/ProgramÀ Files/VERITAS/NetBackup/Logs/user_ops/dbext/logs/5248.0.1258247475
11/14/2009 8:14:22 PM - end writing
cannot connect on socket(25)

Thanks in Advance,

With reagrds,
Mohan.

discussion Filed Under:
Group Ownership:

Comments

rj_nbu's picture
19
Nov
2009
0 Votes 0
Login to vote

logs ?

Hi Mohan, do you have the logs enabled on the media server? BTW what are these servers : lccdb056p1 and lccdb112p1

-Rajeev
"Unix IS user friendly... It's just selective about who its friends are"