Normally, a new backup in dsmsched.log on all servers starts like this:
Executing Operating System command or script:
preschedule.exe
03/12/2013 22:10:01 Finished command. Return code is: 0
03/12/2013 22:10:02 --- SCHEDULEREC OBJECT BEGIN BACKUP_DAILY 03/12/2013 22:00:00
but snapshot image backups start like this:
Executing Operating System command or script:
preschedule.exe
03/16/2013 20:07:49 Finished command. Return code is: 0
03/16/2013 20:07:51 Image backup of volume '\\servername\c$'
Why isn't SCHEDULEREC OBJECT BEGIN placed also to the beginning of snapshot image backups?
I see this behavior of tsm client on windows servers (2003,2008, both 32/64) no matter whether I go to TSM 5.5 clients or to TSM 6.2 clients.
Our TSM server is 5.5.6.
Why isn't there a standard approach for marking start of scheduled backup?
Executing Operating System command or script:
preschedule.exe
03/12/2013 22:10:01 Finished command. Return code is: 0
03/12/2013 22:10:02 --- SCHEDULEREC OBJECT BEGIN BACKUP_DAILY 03/12/2013 22:00:00
but snapshot image backups start like this:
Executing Operating System command or script:
preschedule.exe
03/16/2013 20:07:49 Finished command. Return code is: 0
03/16/2013 20:07:51 Image backup of volume '\\servername\c$'
Why isn't SCHEDULEREC OBJECT BEGIN placed also to the beginning of snapshot image backups?
I see this behavior of tsm client on windows servers (2003,2008, both 32/64) no matter whether I go to TSM 5.5 clients or to TSM 6.2 clients.
Our TSM server is 5.5.6.
Why isn't there a standard approach for marking start of scheduled backup?
