Im on a Windows server that sometimes run very slow and the admin script doesnt finish until next backup session start.
I have put some of the tasks in the script on a timelimit to prevent it from running more then 16 hours. But sometimes that doesnt work and the script is still running the next morning when another admin script is supposed to start.
I have tried to restart the TSM server when this happen but it only result in starting the script that was supposed to run earlier that morning. I.e it wont finish until next backup session.
Since the tasks/process in the script is serial it can take several hours to cancel them, wich I need to do to get a "clean start" the next night.
Is there any way to stop the whole script instead of canceling one process at a time?
And before anyone says "get a faster machine", its in the budget but will still take some time until implemented
I have put some of the tasks in the script on a timelimit to prevent it from running more then 16 hours. But sometimes that doesnt work and the script is still running the next morning when another admin script is supposed to start.
I have tried to restart the TSM server when this happen but it only result in starting the script that was supposed to run earlier that morning. I.e it wont finish until next backup session.
Since the tasks/process in the script is serial it can take several hours to cancel them, wich I need to do to get a "clean start" the next night.
Is there any way to stop the whole script instead of canceling one process at a time?
And before anyone says "get a faster machine", its in the budget but will still take some time until implemented