"dsmc select", whether run by a schedule or manually, does NOT update the last backup date/time. You have to run "dsmc incremental" on a filespace in order to have the last backup date/time updated.
David >>> "Lamb, Charles P." <[EMAIL PROTECTED]> 10/28/2006 9:25 AM >>> Hi...... Regarding our problem below, in the client schedule, we have used select command and in the object field, we have selected individual file systems on the AIX server, i.e. /home, /u02, u03, etc. which are data file systems. Have we set the backup scheme wrong?? On some of the AIX server, we have setup the client schedule with incremental command without any fields in the object field which says to backup all file systems on the AIX server. The TSM filespace header is updated correctly on all filespaces on the AIX server in the TSM system. Thoughts?? -----Original Message----- From: Lamb, Charles P. Sent: Saturday, October 28, 2006 7:27 AM To: 'ADSM: Dist Stor Manager' Cc: Hartman, Thomas J. Subject: RE: [ADSM-L] Days from Last Backup using filespace header question Hi......... When we run a dsmc on a server, the filespace information (backup_end information in the filespace column name from the TSM DB) is updated showing some data has been sent to the TSM system. However, when we run an incremental from the TSM scheduler task list, the filespace information does not show any data has been sent to the TSM system, which is wrong. We are using the select command on the filespace column. Does this make sense?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Saturday, October 28, 2006 7:14 AM To: [email protected] Subject: Re: [ADSM-L] Days from Last Backup using filespace header question On Oct 28, 2006, at 6:58 AM, Lamb, Charles P. wrote: > Hi.... > > We have been running the below script for checking when the server > data > is backup for change management process. We have noticed if the > dsmc is > performed on the server via server scheduler everything is OK with the > filespace header information, however, if we schedule an > incremental via > the TSM scheduler, the filespace header information is not > updated. Has > anyone run across this opportunity?? Thoughts?? > ... Hello, Charles - By "filespace header information", do you mean the Backup_End timestamp? For the server to show a contemporary timestamp for the filespace (or, in 'dsmc query filespace', the "Last Incr Date"), the backup must be an unqualified incremental, which runs to completion. Do 'Query EVent * *' in the TSM server to quickly check schedule completions, and examine the client log file for any issues, include bad return codes. Richard Sims
