adTempus jobs on different servers can be linked. For example, a job on Server B can be run automatically when a job on Server A completes.
adTempus supports distributed scheduling. Distributed scheduling allows you to create and manage jobs on a central "Controller" server and then have those jobs execute on remote "agent" computers.
Remote Administration allows you to run the adTempus Console on a single computer, and administer adTempus servers running on any number of remote computers. That is, you can manage many servers from a single Console. However, each server is configured independently: if you need to run the same job on 10 servers, you must configure that job separately on all 10 servers.
With Distributed Scheduling, jobs are maintained, managed, and monitored on a single Controller server, and changes are propagated automatically to all remote Agent computers.
Distributed scheduling can be used in any of three modes: Basic, Mirror, and Load Balance.
In Basic mode, a job is triggered on the Controller computer, and is then executed on the targeted agent computers. For example, if you want to run the same backup job at the same time on three different servers, you can configure the job on the Controller and select the three servers as Agents. At the scheduled time, the job will run on all three target servers.
In Controller mode, changes made to a job at the Controller are mirrored to the Agents, but the jobs execute independently on all Agents. For example, you have six file servers. On each server you need to run a program whenever files are placed in an upload directory. You can create a job using a File Trigger and have it mirrored to each of these servers. The job will execute on a server when files appear in that server's upload directory, without affecting the other servers.
Agents operating in Mirror mode execute jobs independently of the Controller server, and therefore can continue to function even if the Controller server is unavailable due to server failure, network outage, etc.
In Load Balance mode, you specify a pool of eligible target computers for the job. When the job needs to be executed, adTempus automatically selects a single Agent on which to execute the job, based on the current load on each Agent.