Summary

Although the Arcana Scheduler is not "cluster aware," it can be managed as a generic service in a clustered environment to provide a failover configuration.

Background

The Arcana Scheduler stores information about scheduled programs in a subdirectory named "schedules\1" under the Arcana Scheduler program directory.

User-defined holidays and security settings are stored in the Registry under key "HKEY_LOCAL_MACHINE\Software\Arcana Development\Arcana Scheduler" (note that the Arcana Scheduler online help gives the wrong location).

For more information on the data storage, see the "Technical Information" topic in the Arcana Scheduler online help index.

Arcana Scheduler Installation and Configuration

Because the directory where the Scheduler stores its files is not configurable and is always a subdirectory of the program's installation location, it is not possible to install the Arcana Scheduler locally on each node and have the Scheduler store configuration data on a shared storage device. Instead you must use one of the following approaches:

• On each node, install the Arcana Scheduler software, selecting a directory on the shared storage device as the target for the installation. In this configuration, the two nodes will share both the program files and data files.
• Install the software locally on each node, and use an external process to keep the configuration files synchronized between the two nodes.

In either case, after you have completed your initial configuration you will need to copy the necessary Registry settings between the two computers, if you have customized security or holiday settings.

Clustering Configuration

Using the operating system's cluster administration tools, configure the cluster to manage Arcana Scheduler as a generic service, so that Windows will start adTempus on the secondary node during failover.

Licensing

In an active/passive configuration (where the Arcana Scheduler will only be active on one node at a time), you are only required to purchase a single Arcana Scheduler license. You can use the same license file on both nodes of the cluster.