In order to get a report by TSM, you have to schedule the backup through TSM.
You could query the summary_extended table to get some info, but it's at the session level. So if a backup has 3 sessoins, you would see 3 entries for it. This would give you all the backups in the last 24 hours:
Code:
select * from summary_extended where activity='BACKUP' AND end_time>current_timestamp-24 hours
Then you can use columns like SUCCESSFUL if you cant to get an exception report. So if you have " successful='NO' ", it would only give you those that failed. The COMPLETION_CODE will give you the final RC like you normally see for a TSM schedule: 0,4,8 or 12.
Or to get a list of nodes that have not had a successful backup in the last day:
Code:
select node_name,min(date(BACKUP_END)) as "Last Successful Backup" from filespaces where DAYS(current_date)-DAYS(backup_end)>1 or backup_end is null group by node_name order by min(date(BACKUP_END))
The above query is looking at the filespaces, the last backup date of each filespace is for the last successful backup, not an incomplete backup (one with errors). It doesn't care if the backup was manual or scheduled, scheduled outside TSM is treated like a manual in TSM. You can change the 1 in this section "DAYS(current_date)-DAYS(backup_end)>1" to a larger number if you want don't care about missing 1 days backup, but care about missing 3 days in a row. If there is no date, it means there never was a successful backup.