|
Re: Backup error
2005-12-26 14:03:36
On Dec 26, 2005, at 12:50 PM, Marcelo Barreto wrote:
I ping to that IP without problems, I telnet there and is ok, I
started a backup manually and it´s ok too.
Another suggestion?
...
Just for complete clarity in this problem pursuit:
You logged on to the problem client, performed standard TCP
connectivity testing (the telnet), and initiated a 'dsmc i' command,
and that worked from the problem client?
I´ve one server that cannot backup, in dsmerror.log file I see:
12/22/2005 05:55:15 ANS1809W Session is lost; initializing session
reopen procedure.
12/22/2005 11:19:01 sessSendVerb: Error sending Verb, rc: -50
12/22/2005 11:19:01 ANS1809W Session is lost; initializing session
reopen procedure.
12/22/2005 11:19:02 ANS1809W Session is lost; initializing session
reopen procedure.
12/22/2005 11:19:58 ANS5216E Could not establish a TCP/IP
connection with address '192.168.10.65:1500'. The TCP/IP error is
'Unknown error' (errno = 10060).
12/22/2005 11:19:58 ANS4039E Could not establish a session with a
TSM server or client agent. The TSM return code is -50.
...
Error 10060 is a socket error, labeled WSAETIMEDOUT in the Windows
Socket API, and ETIMEDOUT in Unix TCP/IP programming. It means that
the client timed out waiting for a response from the server. If a
Windows context, Web page http://www.sockets.com/err_lst1.htm will be
helpful in explaining the error and providing some pursuit advice.
Whereas your 192.168 is a private subnet, you may be subject to
foibles in whomever is configuring the router behind which you are
operating. And I presume that the client is within the same subnet,
for it to be able to reach the server at all. Look in the TSM server
Activity Log for the times when the connection failures occur and see
what error messages are recorded there regarding the session: if
none, except that the session disappeared, then that would point to a
networking problem.
If posting more about this problem, please include client and server
platform types and OS types, plus the TSM client-server levels and
some information on the networking there, to give us further
perspective.
Richard Sims
|
|
|
