Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Tue, 24 Oct 2006 08:49:33 -0700

Thanks Dave.
 
I've been pretty wary setting up my buffers in the environment, and haven't changed them for a few months, so I'm relatively confident they're not the issue.
 
Backline support is scratching their heads at the moment...
 
 

From: Clooney, David [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 24, 2006 4:55 AM
To: Dyck, Jonathan; [email protected]
Subject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Couple of technotes regarding buffers,  buffers are a delicate scenario , make sure your read the docs well and understand them before implementing.
 
Also read the tuning performance guide
 
Hope it helps
 
Dave
 
note : if NUMBER_DATA_BUFFERS_RESTORE  is not implemented restores will use NUMBER_DATA_BUFFERS
 
http://seer.entsupport.symantec.com/docs/183702.htm
 
http://seer.support.veritas.com/docs/244652.htm

From: Dyck, Jonathan [mailto:[EMAIL PROTECTED]
Sent: 23 October 2006 17:19
To: Clooney, David; [email protected]
Subject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Yup, that brings up some interesting stuff...
 
 

11:59:48.246 [8168.6708] <2> logconnections: BPRD ACCEPT FROM x.x.x.x. TO x.x.x.x.x

11:59:48.246 [8168.6708] <2> process_request: setsockopt SO_LINGER on 280 succeeded.

11:59:48.246 [8168.6708] <2> connected_peer: Connection from host X, x.x.x.x, on non-reserved port 4584

11:59:48.246 [8168.6708] <2> ParseConfigExA: Unknown configuration option on line 90: RenameIfExists = 0

11:59:48.246 [8168.6708] <2> nb_is_valid_master_server: checking if master_server is a valid server

11:59:49.340 [8168.6708] <2> get_string: buffer space for 3072 bytes, but incoming data needs 218762506 bytes

11:59:49.340 [8168.6708] <2> get_string: (7) inadequate buffer space for data

11:59:49.355 [8168.6708] <32> process_request: get_string() failed - incoming data too large for buffer (0)

11:59:49.355 [8168.6708] <32> process_request: could not process request from master_server


From: Clooney, David [mailto:[EMAIL PROTECTED]
Sent: Monday, October 23, 2006 12:01 PM
To: Dyck, Jonathan; [email protected]
Subject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Agreed , keep a tail on your bprd log on the master to see whats happening at time of restore request..
 
Possible number of allowed tcp connections limitation.
 
Dave

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan
Sent: 23 October 2006 15:58
To: [email protected]
Subject: Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Hmm, seems port 13720 isn't accepting connections...  now to figure out why.
 
Anyone have any advice?
 
 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan
Sent: Monday, October 23, 2006 7:40 AM
To: [email protected]
Subject: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42

Hi all,
Since hardware support and Veritas support seem to be getting nowhere on my problem, thought I'd hit the DL up to see if anyone's run into this problem before.
 
Here's the environment:
  • 1 Wintel Master, 3 Wintel + 3 Solaris media servers(5.1 MP5)
  • SSO, all LTO3 drives visible to all master/media, a single HP ESL712e
  • No firewalls set up between any of these
Here's the problem:
  • Catalog is fully browsable.
  • Backups can be queued manually or scheduled, and run fine in the environment.
  • When submitting a restore (from either a workstation or straight from the master itself, both of which worked perfectly fine up until now, and no changes have been made in the environment),  the GUI hangs up,  takes over 10 minutes to submit, and report back asking that the restore has been submitting successfully and if I want to see its progress.
  • At this point the restore appears in the Activity Monitor and stays in a queued state (for sometimes up to 30 minutes) and then reports back with an SC 42 (network read failed).
I've checked my hardware, switch, application and system logs, and nothing really stands out.  Probably something out there buried in my Veritas logs, but support hasn't been able to tell me anything in over 3 days now (plus a weekend).
 
Any insight out there?  I'd appreciate it!
 
Thanks,
Jon
 
 
 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.


Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.



Notice to recipient:
The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.

When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.

If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.

 
_______________________________________________
Veritas-bu maillist  -  [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to