Veritas-bu

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

2006-10-23 12:00:49
Subject: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42
From: david.clooney at bankofamerica.com (Clooney, David)
Date: Mon, 23 Oct 2006 17:00:49 +0100
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: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Dyck,
Jonathan
Sent: 23 October 2006 15:58
To: veritas-bu at mailman.eng.auburn.edu
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: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Dyck,
Jonathan
Sent: Monday, October 23, 2006 7:40 AM
To: veritas-bu at mailman.eng.auburn.edu
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20061023/f8b0f68c/attachment.html