Sorry, I should have included the dsmerror.log information... 01/17/2007 09:00:46 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 01/17/2007 10:03:26 ANS1512E Scheduled event 'L6S_WED' failed. Return code = 12.
-----Original Message----- From: Litten, David W [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 11:21 AM To: Mcnutt, Larry E. Subject: FW: [ADSM-L] Why is the backup status "Failed"? What does the dsmerror.log say? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mcnutt, Larry E. Sent: Tuesday, January 23, 2007 11:09 AM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Why is the backup status "Failed"? TSM SERVER 5.3.3.0 Client 5.3.2.2 (Win XP laptop) I'm seeing some workstation scheduled backups that get marked as "Failed", but when I look at the details in the dsmsched.log, there aren't any failed files. The only failure is when the scheduler initially tried to contact the TSM server. Then it retries 15 minutes later, and everything works fine. Would this cause the "Failed" status? I'm not sure why the initial connection problem happens, but with mobile units, it is not unusual to have the network connection be transient. It looks like the client is marking the backup as failed, just to "err on the side of caution". It's just a little tedious explaining that the backup is "working fine" to upper management when they get the "Failed" notification. (whine off). Thanks for the shoulder, Larry McNutt 01/16/2007 16:56:30 --- SCHEDULEREC QUERY BEGIN 01/16/2007 16:56:30 --- SCHEDULEREC QUERY END 01/16/2007 16:56:30 Next operation scheduled: 01/16/2007 16:56:30 ------------------------------------------------------------ 01/16/2007 16:56:30 Schedule Name: L6S_WED 01/16/2007 16:56:30 Action: Incremental 01/16/2007 16:56:30 Objects: 01/16/2007 16:56:30 Options: 01/16/2007 16:56:30 Server Window Start: 06:45:00 on 01/17/2007 01/16/2007 16:56:30 ------------------------------------------------------------ 01/16/2007 16:56:30 Command will be executed in 14 hours and 12 minutes. 01/17/2007 09:00:41 Executing scheduled command now. 01/17/2007 09:00:46 Node Name: BICWML34N36T 01/17/2007 09:00:46 Command will be retried in 15 minutes. 01/17/2007 09:15:46 Retrying scheduled event: L6S_WED 01/17/2007 09:15:46 Node Name: BICWML34N36T 01/17/2007 09:15:46 Session established with server FSPHTSM2: AIX-RS/6000 01/17/2007 09:15:46 Server Version 5, Release 3, Level 3.0 01/17/2007 09:15:46 Server date/time: 01/17/2007 09:15:47 Last access: 01/16/2007 16:56:33 01/17/2007 09:15:46 --- SCHEDULEREC OBJECT BEGIN L6S_WED 01/17/2007 06:45:00 01/17/2007 09:15:46 Incremental backup of volume '\\bicwml34n36t\c$' 01/17/2007 09:15:55 Directory--> 0 \\bicwml34n36t\c$\ [Sent] 01/17/2007 09:15:55 Directory--> 0 \\bicwml34n36t\c$\23b12c27ca6ee0a7dfa41c25 [Sent] 01/17/2007 09:15:55 Directory--> 0 \\bicwml34n36t\c$\Application [Sent] **** SNIPPED 01/17/2007 10:03:26 Successful incremental backup of '\\bicwml34n36t\c$' 01/17/2007 10:03:26 --- SCHEDULEREC STATUS BEGIN 01/17/2007 10:03:26 Total number of objects inspected: 72,146 01/17/2007 10:03:26 Total number of objects backed up: 16,541 01/17/2007 10:03:26 Total number of objects updated: 0 01/17/2007 10:03:26 Total number of objects rebound: 0 01/17/2007 10:03:26 Total number of objects deleted: 0 01/17/2007 10:03:26 Total number of objects expired: 0 01/17/2007 10:03:26 Total number of objects failed: 0 01/17/2007 10:03:26 Total number of subfile objects: 0 01/17/2007 10:03:26 Total number of bytes transferred: 2.17 GB 01/17/2007 10:03:26 Data transfer time: 7,567.26 sec 01/17/2007 10:03:26 Network data transfer rate: 301.47 KB/sec 01/17/2007 10:03:26 Aggregate data transfer rate: 797.61 KB/sec 01/17/2007 10:03:26 Objects compressed by: 0% 01/17/2007 10:03:26 Subfile objects reduced by: 0% 01/17/2007 10:03:26 Elapsed processing time: 00:47:40 01/17/2007 10:03:26 --- SCHEDULEREC STATUS END 01/17/2007 10:03:26 --- SCHEDULEREC OBJECT END L6S_WED 01/17/2007 06:45:00 01/17/2007 10:03:26 ANS1512E Scheduled event 'L6S_WED' failed. Return code = 12. 01/17/2007 10:03:26 Sending results for scheduled event 'L6S_WED'. 01/17/2007 10:03:26 Results sent to server for scheduled event 'L6S_WED'. ----------------------------------------- This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
