1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

Cancel admin script?

Discussion in 'Command Line Administrator Client' started by Softish, Sep 13, 2011.

  1. Softish

    Softish New Member

    Dec 7, 2009
    Likes Received:
    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 :)
  3. Harry_Redl

    Harry_Redl Moderator

    Dec 29, 2003
    Likes Received:
    IT Consultant
    Czech Republic

    as far as I know you cannot stop the script processing.
    Automating the process for cancelling all the maintenance jobs before backup starts can be very complicated.

    What about this (just a mental exercise :) )
    a) For each task in the original script create a separate script - the last line of these scripts should update schedule definition for the next script to be run after 5minutes from now with starttdate=today and onetime period (do not modify the "ACTIVE=YES/NO" value)
    With this setup you can break the chain of jobs by setting all the scheduled (administrative) jobs to "ACTIVE=NO"
    b) Schedule the first job to be run at the desired time with ACTIVE=YES

    Now all you have to do is to check (before the backup starts) if any maintenance job is still running - if yes, you set all the other schedules to ACTIVE=NO and cancel the single running process (should be scriptable easily).
    After backup ends, set all the jobs to active again (their startup time and date are in the past so the do not start except the first one)

    It is just an idea, but should work :) Let us know :)


Share This Page