ADSM-L

Scheduled Backup fails to report Success

2000-03-06 14:44:51
Subject: Scheduled Backup fails to report Success
From: John Monahan <JohnMonahan AT LIBERTYDIVERSIFIED DOT COM>
Date: Mon, 6 Mar 2000 13:44:51 -0600
Client:  NT, TSM 3.7.1.0
Server: AS400, ADSM 3.1.1.7

I have a client that shows a failed status for a selective backup every
night (run via the scheduler), but examining the log on the client it looks
like everything succeeded except for the report back to the server of a
success.  There are no errors is the dsmerror.log and here is the client
dsmsched.log:

03/04/2000 00:26:05 --- SCHEDULEREC STATUS BEGIN
03/04/2000 00:26:05 Session established with server LDIHST90: AS400
03/04/2000 00:26:05   Server Version 3, Release 1, Level 1.7
03/04/2000 00:26:05   Server date/time: 03/04/2000 00:21:55  Last access:
03/03/2000 22:35:52

03/04/2000 00:26:05 Total number of objects inspected:   50,100
03/04/2000 00:26:05 Total number of objects backed up:   49,858
03/04/2000 00:26:05 Total number of objects updated:          0
03/04/2000 00:26:05 Total number of objects rebound:          0
03/04/2000 00:26:05 Total number of objects deleted:          0
03/04/2000 00:26:05 Total number of objects failed:           0
03/04/2000 00:26:05 Total number of bytes transferred:     1.81 GB
03/04/2000 00:26:05 Data transfer time:                1,408.57 sec
03/04/2000 00:26:05 Network data transfer rate:        1,347.91 KB/sec
03/04/2000 00:26:05 Aggregate data transfer rate:        127.27 KB/sec
03/04/2000 00:26:05 Objects compressed by:                    0%
03/04/2000 00:26:05 Elapsed processing time:           04:08:37
03/04/2000 00:26:05 --- SCHEDULEREC STATUS END
03/04/2000 00:26:06 ANS1017E Session rejected: TCP/IP connection failure

03/04/2000 00:26:06 --- SCHEDULEREC OBJECT END SRVLTX99DAILY 03/03/2000
20:00:00
03/04/2000 00:26:06 ANS1512E Scheduled event 'SRVLTX99DAILY' failed.
Return code = 4.
03/04/2000 00:26:06 Sending results for scheduled event 'SRVLTX99DAILY'

No other communication problems are happening.  I have another NT ADSM
Server 3.1.2.50 backing up itself with the TSM 3.7.1.0 client that also had
the same error last night, except it uses Named Pipes, but similar error in
the same place.

Any ideas?


John Monahan
Network Administrator
Liberty Diversified Industries
(612) 536-6677
<Prev in Thread] Current Thread [Next in Thread>