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 K 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?
select filespace_name as "Filespace", node_name as "Node Name",
days(current_date)-days(backup_end) as "Days from Last Backup" from
filespaces where (days(backup_end) < (days(current_date)-0)) and
(days(current_date)-9999) < (days(backup_end))

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 K 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