> Do you get them (54 and 50) together?  Just wondering if you get a 54
> (because the db was busy enough that it didn't start the stream in
> time) on the NBU side, then the db sees something goofy is up and
> starts killing the others (but not in a nice way that NBU
> understands).  

> Just a thought.

Yes it seems that way; we tend to get one 54 plus a set of 50's.  The end
times for the 50's seem to be before the end time for the 54 (in xbpmon).
The "auto" schedule that started all of these off finishes with 0 - when
this occurs it is all over in a matter of minutes.  Doesn't always work that
way - sometimes just get one stream failing with 54 and the remainder
completing OK, or some failing and some OK.  It looks to me like what is
happening is once one stream incurs a 54 error that signals for the rest to
fail.

The EBU log seems to bear this out.  I get some tablespaces put into backup
mode, followed by some "Starting BFS" statements for data files being backed
up, follwed by "EBU-4306: Error occured while writing data to tape",
followed by some "BFS in progress xxx cancelled" messages and eventually an
"EBU-2012: Job 12262 failed due to tape management error".  Not sure I
believe these errors as sometimes the same backup can be rerun successfully,
tapes are getting mounted etc.

At the moment of failure recorded in the EBU log the media servers' bpbrm
log records :

04:28:16 [15883] <2> bpbrm listen_for_client_timeout: timed out listening
for th
e client
04:28:16 [15883] <16> bpbrm listen_for_client: listen for client timeout
during
accept from data listen socket after 60 seconds
04:28:16 [15883] <2> bind_on_port_addr: bound to port 47498
04:28:16 [15883] <2> check_authentication: no authentication required
04:28:16 [15883] <2> bpbrm kill_child_process: start
04:28:16 [15883] <4> bpbrm Exit: client backup EXIT STATUS 54: timed out
connect
ing to client

According to Veritas this 60 second timeout is BPCD_ACCEPT_TIMEOUT and is
not tunable.

Phil Weber
Egg



This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies comprises Prudential Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  All members of the Egg group
are registered in England and Wales. Registered offices: 142
Holborn Bars, London EC1N 2NH

If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.