Todd,

I had a number of difficulties with the scheduler on NT and my particular
environment (I needed to synchronise three systems to issue OS level
commands which would themselves invoke ADSM's API).  In the end the easiest
way for me was to run a batch file using NT's OS level scheduler service on
each machine.

I have three systems to backup and only two tape drives.  I don't want
conflicting mount requests from multiple sessions from different nodes and
each "backup" job will execute between forty and fifty sessions.  I have
scheduled one job to run on my production machine and, on completion, to
trigger the appropriate job on the test machine.  Quite independently a
backup job is scheduled on our develpment machine.  The ADSM server knows
nothing about the schedule until each node presents it with a backup
session request.  By using a .bat file to spawn itself onto the test
machine, I ensure that production backups have finished with one tape drive
before the test system tries to use it.  This ensures that the other tape
drive is able to be dedicated to the development backup and there is no
need for manual intervention unless a tape actually fills up.

Murray Nicholas
Systems Specialist
HALTEK PTY LTD