We had a lot of problems with 50s and 54s on RMAN backups a while back, and
fixed by bringing the NB client and NB database client software up to the
same patch levels as the master and media servers.

I seem to remember 52s can be caused by having the
/usr/openv/volmgr/DISABLE_RESOURCES_BUSY flag set on your master server.  I
think this is a hangover from 3.4 but now strongly dis-recommended by
Veritas (see support.veritas.com).  This flag was pointed out to us by
Veritas on a support call for performance issues, although we weren't
getting 52s.

regards, Phil

-----Original Message-----
From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com] 
Sent: 09 August 2004 16:16
To: Mark.Donaldson AT cexp DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Error 54 - client connect timeout


Well - I've changed the symptoms.

I'm getting Error 52's now.  Timeouts on Media Mounts.

I've changed the storage unit to a fixed unit from the former storage group
and set my media mount timeouts to zero per this document:

http://seer.support.veritas.com/docs/263989.htm

-M

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Donaldson,
Mark - Broomfield, CO
Sent: Friday, August 06, 2004 1:47 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Error 54 - client connect timeout


Well - what I've done so far:

First off, the storage units are already set to a fixed storage group &
their bp.conf files contain the MUST_USE_LOCAL_DRIVES directive so the media
servers are using their locally defined storage unit as the destination.

My CLIENT_READ_TIMEOUT was already set to 7200 but CLIENT_CONNECT_TIMEOUT
was only 500 so I upped it to 1800 (Thanks, Penelope & Glenda).

I've set my Netbackup max-jobs/client for these clients to 99 (from 12 - a
mistake but it was still there) since they're media servers and I pretty
much let the media servers run wide open.  (The change to 12 jobs/client was
only recent and we've been plagued by these type of errors for longer than
this so I don't think this is too relevant.)

My master server's tcp time wait interval was still at default (120000 ms)
so I dropped it to 10000.  I also increased the default window sizes to 64K
(tcp_xmit_hiwat & tcp_recv_hiwat) from their defaults.  This matches my
master server's settings to these clients' already set values.  I also
increased the master server's TCP queue size (tcp_conn_req_max_q) to 2048
from 1024.

Backups are running now and I'm monitoring.  

They'd start before - no problem - but would often have trouble completing
after hours of running.  I'll see where they are this weekend and update
this note on Monday.

Thanks to all who replied.

-M

-----Original Message-----

I'm being plagued by these on my RMAN backups:

ERROR: 54
timed out connecting to client
The server could not complete the connection to the client. The accept
system or winsock call timed out after 60 seconds.

I've got an open ticket with Veritas but have any of you defeated this
dragon?

-M

=================================================
 (2B|^2B) == ?
=================================================
 Mark Donaldson - SA - Corporate Express
=================================================
_______________________________________________
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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
is authorised and regulated by the Financial Services Authority. Egg
Investments Ltd. is entered in the FSA register under number 190518. 

Registered in England and Wales. Registered offices: 1 Waterhouse
Square, 138-142 Holborn, London EC1N 2NA.

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.