I'm guessing this has nothing to do with SQL, and a backup of the problem
machine's file system would also fail with a 54. There's three common
errors in the 50's. 59 means you could contact the client, but bpcd wasn't
running on the machine. 54 is usually you could connect and bpcd wasn't
running, but the media server trying to do the backup wasn't listed as a
server on the client (or in the event of ALL_LOCAL_DRIVES, the master wasn't
listed, as it has to first make contact with the client to determine how
many jobs are needed). And lastly, you can often get 57, which usually
boils down to you get to the client on bpcd, and the calling machine is
listed as a server, but when that socket is dropped as per procedure, and a
new one is tried originating from the client for the actual backup data, the
client was unable to call back.
So it looks like the media server trying to make the connection isn't listed
as a server on the client. Try putting in all the hostnames for it as
servers on the client, both FQ & short.
Gregg
-----Original Message-----
From: effendy yahaya [mailto:darkburst AT yahoo DOT com]
Sent: Friday, August 24, 2001 5:37 AM
To: Veritas Mailling List; Penelope Carr;
fx______[François-Xavier_Peretmere]
Subject: [Veritas-bu] SQL client - status code 54
Hi,
NBU Data center 3.4 GA, database extension SQL.
master, media and client sittin on Win2K.
SAN environment, TL891 Compaq minilibrary.
I had installed SQL extension to a client and on top
of microsoft cluster. The ODBC and SQL client
configuration are basically on the same setting for
both cluster and non-cluster machine. Unfortunately,
the client machine (non-cluster) can't do the backup.
Basically, from the OS fullbackup it's works fine.
SQL backup had give me a status code 54 as below:
timed out connecting to client
------------------------------
The server could not complete the connection to the
client. The accept system call timed out after 60
seconds.
I have checked the network routing, hostname and also
did increased the client connect timeout to 1800
seconds on the clients, master and media machine.
I'm configured this client to get the
DOMAIN/Administrator grant privilledges for both NBU
and SQL services.
What was the really problem ? Do I need to increase
the page cache or what ? I did turn on and configure
the OTM for the basic need for that machine.
Best regards,
Effendy Yahaya
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
