Be sure that the media type identifier is correct.  If the system thinks
it's mounting a DTL and you have a HCART it will puke.

Thank you,
 
 
Samuel J. Coco, STG
Functional Area Manager, ARL
Sr UNIX Administrator
BELL      301 394-1151 DSN 290
CELL (B) 240 398-7121 / (H)443 496-1623
HOME     410 604-2415
Email  scoco AT arl.army DOT mil


-----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
Mark.Donaldson AT cexp DOT com
Sent: Monday, August 09, 2004 11:16 AM
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