Alerts/Reporting

Alerts

The collector part of TSMManager maintains a realtime watch on all messages issued by your TSM server. If an error message is encountered, it will immediately send an e-mail to one or more receivers.

You decide what severity should trigger an alert and you also have a filtering capability to filter out "harmless" error messages.

You can setup certain users to receive an alert e-mail, if a node they are responsible for fails its scheduled backup.

Reporting

Once every 24 hours, at a time you decide, TSMManager will collect information about all abnormal events in your TSM server, format them and send them as an e-mail to one or more receivers. In addition to that, the report will be stored on the builtin webserver for easy access from a webbrowser.
The information collected includes :

All limits are user adjustable and you can select which items you want included in the report.

Below you see an example of what a report may look like :

TSM status for Linux1 at 26-11-2003 21:05:06

The following client schedules have not completed :
Time Schedule Node Status 15 day history (oldest - newest)
11/26/2003 19:40:00 ORABACKUP TSM1_ORACLE Missed
                             
11/26/2003 19:50:00 SQLBACKUP TSM1_MSSQL Missed
                             
11/26/2003 20:00:00 INCR2000 TSM1 Missed
                             

Backups with failed files
Node Number of failed files
METTE 1
THOMAS 1

The following clients have not been in contact with the server during the last 30 hours :
Node Last access
DELLEN 2003-11-21 18:30:45
MSSQL1 2003-10-12 13:51:46
MSSQL2 2003-10-12 13:51:59
MSSQL3 2003-10-12 13:52:12
TEST1 2003-10-07 10:17:44
 
The following filespaces have not completed their backup within the last 3 days :
Node Filespace name Last backup complete
DELLEN SYSTEM OBJECT 2003-11-21 19:25:02
DELLEN \\dellen\c$ 2003-11-21 19:10:36
MSSQL1 TSM1.Northwind 2003-10-12 13:51:58
MSSQL1 TSM1.master 2003-10-12 13:51:50
MSSQL1 TSM1.model 2003-10-12 13:51:51
MSSQL1 TSM1.msdb 2003-10-12 13:51:55
MSSQL1 TSM1.pubs 2003-10-12 13:51:57
TSM1 SYSTEM OBJECT 2003-10-06 20:20:41
TSM1 \\tsm1\c$ 2003-10-06 20:07:12
TSM1 \\tsm1\d$ 2003-10-06 20:14:08
TSM1 \\tsm1\f$ 2003-10-06 20:14:08
TSM1_MSSQL TSM1.Northwind 2003-10-12 13:51:42
TSM1_MSSQL TSM1.master 2003-10-12 13:51:30
TSM1_MSSQL TSM1.model 2003-10-12 13:51:34
TSM1_MSSQL TSM1.msdb 2003-10-12 13:51:38
TSM1_MSSQL TSM1.pubs 2003-10-12 13:51:40
TSM1_ORACLE \adsmorc 2003-10-12 13:51:26
 
Summary of client activity for the last 24 hours
Domain Nodename Platform Activity Data amount Elapse time Affected Failed Media wait
STANDARD ELIZABETH WinNT BACKUP 316,8 MB 0 00:17:21 2206 0 0
STANDARD JAN WinNT BACKUP 504,2 MB 0 00:08:20 2698 0 0
STANDARD LINUX1 Linux86 BACKUP 4,3 MB 0 00:07:22 180 0 0
STANDARD METTE WinNT BACKUP 241,2 MB 0 00:04:50 2342 1 0
STANDARD THOMAS WinNT BACKUP 213,1 MB 0 00:03:04 2303 1 0
 
The following DISK storagepools are more than 80 % utilized
DISKPOOL 80.6
PROGDATA 80.7
 
The following volumes are less than 25 % utilized. (Is reclaim working ?)
Volume Storage pool
TSMBACK.BFS.069545636 COPYPOOL
 
The following servers/storage agents are not active :
Server/storage agent Description Address Last access
STAJAN Storage agent on JAN 192.168.1.6 2003-03-07 21:31:58
TSM1 Windows TSM server 192.168.1.15 2003-07-20 19:03:31
TSMBACK 80.62.159.35 2003-11-26 03:07:22
 
Messages for the last 24 hours :
2003-11-26 01:00:22 ANR6752W Disaster recovery manager operation BACKUP STGPOOL is in violation of server license terms - server is not licensed for disaster recovery manager support.
2003-11-26 01:02:01 ANR6752W Disaster recovery manager operation BACKUP DB is in violation of server license terms - server is not licensed for disaster recovery manager support.
2003-11-26 19:50:01 ANR2578W Schedule ORABACKUP in domain STANDARD for node TSM1_ORACLE has missed its scheduled start up window.
2003-11-26 20:00:01 ANR2578W Schedule SQLBACKUP in domain STANDARD for node TSM1_MSSQL has missed its scheduled start up window.
2003-11-26 20:20:01 ANR2578W Schedule INCR2000 in domain STANDARD for node TSM1 has missed its scheduled start up window.