The dsmsched.log file can be found linked under your Backup folder on your desktop (sometimes renamed as auto-backup).
It can be also found under the backup client installation directory (C:\Program Files\Tivoli\TSM\baclient) (/tmp/dsmsched.log and /tmp/dsmerror.log for linux users)
Open the file with notepad or an other text editor, and scroll at the END of the file to see the latest log entries
The following example does explain how to check your backup status.
A successful backup session does look like this under dsmsched.log:
08/12/2020 11:19:17 --- SCHEDULEREC STATUS BEGIN
08/12/2020 11:19:17 Session established with server TSM_B: Linux/x86_64
08/12/2020 11:19:17 Server Version 8, Release 1, Level 6.100
08/12/2020 11:19:17 Server date/time: 08/12/2020 11:20:25 Last access: 08/12/2020 11:19:37
08/12/2020 11:19:17 Total number of objects inspected: 205,000
08/12/2020 11:19:17 Total number of objects backed up: 7,838
08/12/2020 11:19:17 Total number of objects updated: 0
08/12/2020 11:19:17 Total number of objects rebound: 0
08/12/2020 11:19:17 Total number of objects deleted: 0
08/12/2020 11:19:17 Total number of objects expired: 558
08/12/2020 11:19:17 Total number of objects failed: 0
08/12/2020 11:19:17 Total number of objects encrypted: 0
08/12/2020 11:19:17 Total number of subfile objects: 0
08/12/2020 11:19:17 Total number of objects grew: 0
08/12/2020 11:19:17 Total number of retries: 928
08/12/2020 11:19:17 Total number of bytes inspected: 178.90 GB
08/12/2020 11:19:17 Total number of bytes transferred: 19.70 GB
08/12/2020 11:19:17 Data transfer time: 2,188.09 sec
08/12/2020 11:19:17 Network data transfer rate: 9,438.77 KB/sec
08/12/2020 11:19:17 Aggregate data transfer rate: 7,566.85 KB/sec
08/12/2020 11:19:17 Elapsed processing time: 00:45:29
08/12/2020 11:19:17 --- SCHEDULEREC STATUS END
08/12/2020 11:19:17 --- SCHEDULEREC OBJECT END DAILY 08/12/2020 08:00:00
08/12/2020 11:19:17 Scheduled event 'DAILY' completed successfully.
08/12/2020 11:19:17 Sending results for scheduled event 'DAILY'.
The line "Scheduled event 'DAILY' completed successfully",does mean that the auto-backup did finish successfully
Instead a failed backup can look like this:
...
09/11/2020 20:35:57 ANS1228E Sending of object '\\lt675\c$\Users\viertler\AppData\Local\Temp\mozilla-temp-files\mozilla-temp-41' failed.
09/11/2020 20:35:57 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Local\Temp\mozilla-temp-files\mozilla-temp-41': the object is in use by another process
09/11/2020 20:35:58 ANS1228E Sending of object '\\lt675\c$\Users\viertler\AppData\Local\TileDataLayer\Database\vedatamodel.edb' failed.
09/11/2020 20:35:58 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Local\TileDataLayer\Database\vedatamodel.edb': the object is in use by another process
09/11/2020 20:36:52 ANS1228E Sending of object '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_0' failed.
09/11/2020 20:36:52 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_0': the object is in use by another process
09/11/2020 20:36:52 ANS1228E Sending of object '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_1' failed.
09/11/2020 20:36:52 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_1': the object is in use by another process
09/11/2020 20:36:52 ANS1228E Sending of object '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_3' failed.
09/11/2020 20:36:52 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_3': the object is in use by another process
09/14/2020 09:59:00 ANS1809W A session with the IBM Spectrum Protect server has been disconnected. An attempt will be made to reestablish the connection.
09/14/2020 09:59:00 ... failed
09/14/2020 09:59:00 ANS1809W A session with the IBM Spectrum Protect server has been disconnected. An attempt will be made to reestablish the connection.
09/14/2020 09:59:00 --- SCHEDULEREC STATUS BEGIN
09/14/2020 09:59:00 Total number of objects inspected: 107,174
09/14/2020 09:59:00 Total number of objects backed up: 6,189
09/14/2020 09:59:00 Total number of objects updated: 0
09/14/2020 09:59:00 Total number of objects rebound: 0
09/14/2020 09:59:00 Total number of objects deleted: 0
09/14/2020 09:59:00 Total number of objects expired: 3,473
09/14/2020 09:59:00 Total number of objects failed: 43
09/14/2020 09:59:00 Total number of objects encrypted: 0
09/14/2020 09:59:00 Total number of subfile objects: 0
09/14/2020 09:59:00 Total number of objects grew: 0
09/14/2020 09:59:00 Total number of retries: 193
09/14/2020 09:59:00 Total number of bytes inspected: 69.83 GB
09/14/2020 09:59:00 Total number of bytes transferred: 26.82 GB
09/14/2020 09:59:00 Data transfer time: 19,140.06 sec
09/14/2020 09:59:00 Network data transfer rate: 1,469.24 KB/sec
09/14/2020 09:59:00 Aggregate data transfer rate: 123.74 KB/sec
09/14/2020 09:59:00 Objects compressed by: 0%
09/14/2020 09:59:00 Total data reduction ratio: 61,60%
09/14/2020 09:59:00 Subfile objects reduced by: 0%
09/14/2020 09:59:00 Elapsed processing time: 63:07:31
09/14/2020 09:59:00 --- SCHEDULEREC STATUS END
09/14/2020 09:59:00 --- SCHEDULEREC OBJECT END DAILY 09/11/2020 18:00:00
09/14/2020 09:59:00 ANS1512E Scheduled event 'DAILY' failed. Return code = 12.
09/14/2020 09:59:00 Sending results for scheduled event 'DAILY'.
In this case the backup does fail and a Return code 12 has been issue as result.
In this particular case because there are 43 objects always in use during the backup session, and the backup client cannot back up them (ANS4987E error)
09/11/2020 20:36:52 ANS4987E Error processing '\\lt675\c$\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache\data_0': the object is in use by another process
So we can exclude the C:\Users\viertler\AppData\Roaming\Microsoft\Skype for Desktop\Cache directory to prevent those error messages in the future.
In order to do this, please follow the set EXCLUDE and INCLUDE option guide.(here the guide for Linux users)
Other possible client return codes are explained here under the official IBM documentation: client return codes
If your backup does end as FAILED and you do not understand why:
- Open the dsmerror.log file with nothepad or other editor (this file does log ONLY error messages from backup client)
- Take note of the latest error message.
- Send an email to storage-support@pik-potsdam.de with the error message as subject or description the error.Please do also attach the dsmerror.log and dsmsched.log files.Those files are fundamental to let me understand were the error/problem could be.
