Prevent clearing events after updating client schedule ?

[vilius.m]

Helllo,

TSM v7.1

I want to disable client schedule for some interval and enable it again by using command:

update sched dom1 sched1 expiration=-1
...
update sched dom1 sched1 expiration=never

however that action clears all past events associated with sched1 schedule - I do not want that to happen..

Is there any way/workaround not to clear client schedule events while updating it ?

Thanks,
Vilius M.

 

[marclant]

Yes, it's a known defect: https://www-01.ibm.com/support/docview.wss?uid=swg1IT13902

Upgrade to 7.1.6 or greater. Keep in mind if you go over 7.1.8 that this enables SSL for client authentication, so read up on that before upgrading.

 

[moon-buddy]

Helllo,

TSM v7.1

I want to disable client schedule for some interval and enable it again by using command:

update sched dom1 sched1 expiration=-1
...
update sched dom1 sched1 expiration=never

however that action clears all past events associated with sched1 schedule - I do not want that to happen..

Is there any way/workaround not to clear client schedule events while updating it ?

Thanks,
Vilius M.

One way, is to stop the TSM scheduler for nodes that you want to stop backup. You just have to content with missed backups on your daily report unless you can exclude these.

 

[marclant]

One way, is to stop the TSM scheduler for nodes that you want to stop backup. You just have to content with missed backups on your daily report unless you can exclude these.

Along the same lines, if the number of nodes is not too large, you could disassociate them from the schedule on the server and associate them later. That's not considered an update of the schedule, so it would not prevent older events from being displayed.