The following settings are automatically replicated from the primary node to the secondary node:
The configuration file miccfg.xml, which contains most MOVEit Automation settings, including definitions of tasks, hosts, scripts, SSH keys, date lists, and so on.
The StateFiles folder, which contains various XML configuration files specific to individual hosts/tasks. Each “state” file contains information such as date/timestamps for determining file newness, saved directory listings for synchronization tasks, and more.
The tamper detection file michash.xml, which contains information used to detect tampering of the database.
The PGP keyrings, PGPPath\secring.pgp and PGPPath\pubring.pgp. These files contain the PGP keys used by MOVEit Automation, if the optional PGP capability has been licensed.
The MICSTATS database, a database which contains a record of tasks that were run, files that were transferred, and administrator actions that were performed.
Creation, deletion, and other manipulation of local Windows users and groups used to access MOVEit Automation. (Domain users and groups don't need to be replicated as long as both failover nodes are members of the same domain.)
SSL certificates, in the Microsoft Windows certificate store. This includes:
Client certificates, with private keys, optionally used to identify MOVEit Automation when connecting to secure FTP and MOVEit Transfer servers.
Server certificates, with private keys, used to secure communications with MOVEit Automation Admin.
Other people's certificates, without private keys, used for sending S/MIME email (a rarely used capability).
The following are not replicated:
The registry key, which can be found in one of the following locations:
This key contains infrequently-changed settings such as the license key, the directory used for temporary files, and so on. These settings are maintained by the MOVEit Automation configuration program. If you run this configuration program and make changes on one node, you should make those same changes to the other node.
The temporary "cache" directory. Any files stored temporarily by a running task are not replicated to the secondary node. The state of any tasks that were running are lost. Those tasks will be run at the next normally scheduled interval on the secondary node after it takes over.
