Re: [Veritas-bu] Weird error 54/41
2008-02-14 02:09:14
Hi,
Funny, it seems that I posted a reply about a reinstall of the software,
but doesnt seem to have been seen on the list.
Can you advise if this helps sort the problem out?
Simon
Hi
all
Thanks for all replies
received so far. We are busy going through a process of elimination to find out
where the problem is.
Of course the customer
is saying ‘nothing has changed’.
For now we are going to
remove the Oracle agent, reinstall, relink.
All comms are resolving
fine (bpclntcmd in all directions, telnet to ports, etc) – as I’ve said before,
O/S backups are working fine.
Will let you
know
Kind
regards
From: Tim Hoke
[mailto:thoke AT northpeak DOT org] Sent: 12 February 2008 16:46 To: Michael Graff Andersen Cc: Marianne Van Den Berg;
veritas-bu AT mailman.eng.auburn DOT edu Subject: Re: [Veritas-bu] Weird error
54/41
I would not suggest increasing the
CLIENT_CONNECT_TIMEOUT. Think about it, how long *should* it take to
establish a connection between hosts? Essentially, this is equivalent to
how long does it take to establish a telnet session between two hosts? If
it takes you two hours, there's something wrong. I can see that if you are
bouncing your connection over multiple satelite connections, maybe you'd need to
be worried about it, but in general, NetBackup's default of 300 seconds is
MORE than generous.
As for your status 54/41, what changed 3 weeks
ago? Can you establish connections between the client/servers
involved? Ie, can you telnet between them all, etc? Is name
resolution still working? (Run bpclntcmd on each host with the peer
hostname and ip).
-Tim
On 2/12/08, Michael Graff Andersen <mian71 AT gmail DOT com>
wrote:
I have had luck with raising the CLIENT_CONNECT_TIMEOUT
& CLIENT_READ_TIMEOUT settings with this kind of errors
before
Can see you already have raised CLIENT_READ_TIMEOUT,
will suggest that you raise CLIENT_CONNECT_TIMEOUT to the
same
2008/2/12, Marianne Van Den Berg <mvdberg AT stortech.co DOT za>:
Hi
Simon
I appreciate every bit
of advice at this point in time.
I have used NOSM in the
past where the media server is backing up itself. In this case the client
(Linux) is backed up over the network to a media server
(Solaris).
Kind
regards
Hi
Marianne
Not
sure if this helps...
http://seer.support.veritas.com/docs/186016.htm
Pretty sure the creation of a NOSHM
file helped.
S.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Marianne Van Den
Berg Sent: Tuesday, February
12, 2008 10:47 AM To: veritas-bu AT mailman.eng.auburn DOT edu Subject: [Veritas-bu] Weird error
54/41
Hi
all
We
have Oracle rman backups failing with Network Connect
Timeout.
Filesystem backups are working fine.
Weird thing is we can see in Job
details 'Connecting, Connected':
02/12/2008 10:32:29 -
connecting
02/12/2008 10:32:40 -
connected; connect time:
0:00:00
02/12/2008 10:32:40 -
begin writing
02/12/2008 11:32:41 -
end writing; write time: 1:00:01
network
connection timed out
(41)
Handshaking in bpcd on client and
bpbrm on media server is successful.
I
have now increased Client Read Timeout to 7200. Backup 'Active' for 1 hr 54
minutes already – still not a single byte written….
Backups on this client have been
successful till about 3 weeks ago. NetBackup 6.0 MP4 on server and
client.
RMAN backups on the client to local
disk start writing almost immediately.
RMAN log on client
:
ORA-19511: Error received from
media manager layer, error text:
VxBSACreateObject:
Failed with error:
Server
Status: Communication with the server has not been initiated or the server
status has not been retrieved from the server.
PLEASE
HELP!!
This email (including any
attachments) may contain confidential and/or privileged information or
information otherwise protected from disclosure. If you are not the
intended recipient, please notify the sender immediately, do not copy
this message or any attachments and do not use it for any purpose or
disclose its content to any person, but delete this message and any
attachments from your system. Astrium disclaims any and all liability
if this email transmission was virus corrupted, altered
or falsified. --------------------------------------------------------------------- Astrium
Limited, Registered in England and Wales No.
2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage,
Hertfordshire,
SG1 2AS, England |
_______________________________________________ Veritas-bu
maillist - Veritas-bu AT mailman.eng.auburn DOT edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________ Veritas-bu
maillist - Veritas-bu AT mailman.eng.auburn DOT edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
|
|
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|