Table of contents
The following solution assumes that you have requested data backup services for your server or workstation through the Division of Information Technology's (IT) hosted Data Backup Service. This process assumes you have received a confirmation of node registration email from the Division of IT and that you have attempted to install and configure IBM's Spectrum Protect (aka:TSM) Backup/Archive Client on the registered server or workstation.
Tivoli Storage Manager client failed event notification
Now that you have configured IBM Spectrum Protect (aka: TSM) onto your computer/laptop you need to check to make sure everything is configured correctly. If it is not, you will receive an email from backups-help@umd.edu with a Subject line of ISP Client Failed Event Notification.
When you open the email it will provide some help in figuring out what went wrong with the backup.
Check the TSM client daily for backup status
You cannot tell from the client if a backup has happened, so the easiest way is to examine the TSM client logs. These are found in varying locations depending on the platform. The table below will provide the defaults. If you are unsure about where to find the logs, contact your system administrator to determine if TSM has been setup in a non-standard manner.
| Platform | Default TSM Log Location |
| Windows | C:\Program Files\tivoli\tsm\baclient |
| UNIX/Linux | /opt/tivoli/tsm/client/ba/bin |
| Glue UNIX/Linus | /var/tsm |
| Mac OS | /Library/Logs/tivoli/tsm |
Navigate to the appropriate directory either using Explorer for Windows, terminal for Unix/Linux or Finder for Mac.
There should be at least two logs, dsmsched.log (the scheduler log) and the dsmerror.log (general error log). The dsmsched.log will provide the most information on your TSM activity, including information on when the client queries the server for its scheduled tasks, what's been backed up, what files have been expired, and what errors have been generated. Examine this file for verification that a particular set of files are being backed up or at least examined. When an error message is received from TSM administrators, the dsmerror.log will help isolate any fault conditions TSM has encountered. Between these two log files, the TSM administrators will be able to troubleshoot most of the problems that regularly occur with TSM.
Verifying scheduled backup with example
If you have elected to run manual backups for your server or workstation, you will have to monitor nightly backup operations via your own supplied resources or scheduling tool (e.g. cron, Windows Event Manager, etc.). If you have registered your machine with a scheduled backup time through TSM, continue reading to verify that your schedule backups are running as expected.
A sample output is below:
01/23/2015 13:23:58 Normal File--> 19,574 \\name_desktop-win2k1\c$\Windows\System32\Macromed\Flash\FlashInstall.log [Sent]
01/23/2015 13:23:58 Expiring--> 651,440 \\name_desktop-win2k1\c$\Windows\System32\Macromed\Flash\FlashUtil64_16_0_0_257_Plugin.exe [Sent]
01/23/2015 13:23:58 Normal File--> 651,440 \\ name_desktop -win2k1\c$\Windows\System32\Macromed\Flash\FlashUtil64_16_0_0_287_Plugin.exe [Sent]
01/23/2015 13:23:58 Expiring--> 23,048,368 \\ name_desktop -win2k1\c$\Windows\System32\Macromed\Flash\NPSWF64_16_0_0_257.dll [Sent]
01/23/2015 13:23:59 ANS1228E Sending of object '\\ name_desktop -win2k1\c$\Windows\System32\LogFiles\Sum\Svc.log' failed.
01/23/2015 13:23:59 ANS4987E Error processing '\\sfuentes-win2k1\c$\Windows\System32\LogFiles\Sum\Svc.log': the object is in use by another process
01/23/2015 13:23:59 Normal File--> 23,048,368 \\ name_desktop -win2k1\c$\Windows\System32\Macromed\Flash\NPSWF64_16_0_0_287.dll [Sent]
01/23/2015 13:23:59 Normal File--> 136,507 \\ name_desktop -win2k1\c$\Windows\System32\Macromed\Flash\plugin.vch [Sent]
01/23/2015 13:23:59 Directory--> 0 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash [Sent]
01/23/2015 13:23:59 Normal File--> 25,594 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashInstall.log [Sent]
01/23/2015 13:23:59 Normal File--> 856 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\flashplayer.xpt [Sent]
01/23/2015 13:23:59 Expiring--> 1,880,752 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashPlayerPlugin_16_0_0_257.exe [Sent]
01/23/2015 13:23:59 Normal File--> 1,880,752 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashPlayerPlugin_16_0_0_287.exe [Sent]
01/23/2015 13:23:59 Normal File--> 267,440 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe [Sent]
01/23/2015 13:23:59 Expiring--> 960,176 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_257_Plugin.exe [Sent]
01/23/2015 13:23:59 Normal File--> 960,176 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\FlashUtil32_16_0_0_287_Plugin.exe [Sent]
01/23/2015 13:23:59 Expiring--> 16,844,464 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_257.dll [Sent]
01/23/2015 13:23:59 Normal File--> 16,844,464 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\NPSWF32_16_0_0_287.dll [Sent]
01/23/2015 13:23:59 Normal File--> 372,727 \\ name_desktop -win2k1\c$\Windows\SysWOW64\Macromed\Flash\plugin.vch [Sent]
01/23/2015 13:23:59 ANS1802E Incremental backup of '\\ name_desktop -win2k1\c$' finished with 19 failure(s)
01/23/2015 13:24:02 --- SCHEDULEREC STATUS BEGIN
01/23/2015 13:24:02 Total number of objects inspected: 176,927
01/23/2015 13:24:02 Total number of objects assigned: 103,716
01/23/2015 13:24:02 Total number of objects backed up: 557
01/23/2015 13:24:02 Total number of objects updated: 0
01/23/2015 13:24:02 Total number of objects rebound: 0
01/23/2015 13:24:02 Total number of objects deleted: 0
01/23/2015 13:24:02 Total number of objects expired: 18
01/23/2015 13:24:02 Total number of objects failed: 19
01/23/2015 13:24:02 Total number of objects encrypted: 0
01/23/2015 13:24:02 Total objects deduplicated: 392
01/23/2015 13:24:02 Total number of objects grew: 0
01/23/2015 13:24:02 Total number of retries: 198
01/23/2015 13:24:02 Total number of bytes inspected: 42.88 GB
01/23/2015 13:24:02 Total number of bytes processed: 56.77 MB
01/23/2015 13:24:02 Total bytes before deduplication: 474.95 MB
01/23/2015 13:24:02 Total bytes after deduplication: 61.61 MB
01/23/2015 13:24:02 Total number of bytes transferred: 22.33 MB
01/23/2015 13:24:02 Data transfer time: 1.49 sec
01/23/2015 13:24:02 Network data transfer rate: 15,328.06 KB/sec
01/23/2015 13:24:02 Aggregate data transfer rate: 42.28 KB/sec
01/23/2015 13:24:02 Objects compressed by: 68%
01/23/2015 13:24:02 Deduplication reduction: 87.03%
01/23/2015 13:24:02 Total data reduction ratio: 99.95%
01/23/2015 13:24:02 Elapsed processing time: 00:09:00
01/23/2015 13:24:02 --- SCHEDULEREC STATUS END
01/23/2015 13:24:02 --- SCHEDULEREC OBJECT END OSFILES-WEEKDAY-INCR-1300 01/23/2015 13:00:00
01/23/2015 13:24:02 Scheduled event 'OSFILES-WEEKDAY-INCR-1300' completed successfully.
01/23/2015 13:24:02 Sending results for scheduled event 'OSFILES-WEEKDAY-INCR-1300'.
01/23/2015 13:24:02 Results sent to server for scheduled event 'OSFILES-WEEKDAY-INCR-1300'.
Examine this file for verification that a particular set of files is being backed up or at least examined. When an error message is received from ISP administrators, the dsmerror.log will help isolate any fault conditions ISP has encountered. Between these two log files, the ISP admins will be able to troubleshoot most of the problems that regularly occur with ISP.
Test restores
To be certain that a set of files has been backed up and that is able to be restored, it is recommended that you verify by performing test restores on a regular basis. To do a test restore, simply select a small subset of data that you'd like to test.