Summary
This article describes how to prevent the same jobs from executing on two different servers when you migrate an adTempus installation to a new server.
Background Information
When you transfer an adTempus instance to a new server, the recommended approach is to copy or move the adTempus database in its entirety, rather than using export/import to transfer individual jobs.
One thing to be aware of with this approach is that the new adTempus server will start evaluating triggers and executing jobs when you start it. This may produce undesirable results if your jobs are also still running on the original server, as jobs will now be executing on both servers.
Workaround
Generally you will want to prevent jobs from running on the new server until you have reviewed the new installation and configuration, and possibly tested jobs individually. The recommended approach for doing so is as follows:
- Before installing adTempus on the new server, set a Registry option to disable job execution on the server:
- For adTempus 4 and later, refer to "Disable job execution using a Registry option" in the Disable Execution for All Jobs help topic
- For adTempus 3 and earlier, refer to this article.
- Install adTempus on the server.
- Once the software is installed and started, run the Console. You can now use the Hold options in the Console to disable all or some jobs until you have confirmed they work as desired. Note: adTempus will not run any jobs while the Registry option is set, even if you run them manually.
- Once the jobs are disabled, remove the Registry option you set in step 1. Then restart the adTempus service. You can now run jobs manually, or enable jobs to be run automatically.
See Also
