An installation can use MOVEit Automation to copy critical files to a remote server for backup to tape, or to configure a hot standby.
Back up the following critical files and folders regularly. They are located in the Program Files\MOVEit directory.
Critical files.
Critical folders. Back up the folders and their contents.
Note: The configuration file and state files are encrypted. Before you can make changes to them, you must first use MOVEit Automation Admin to authenticate to MOVEit Automation..
Statistics database.
Back up the Statistics database regularly. This information is stored in a database.
Client certificates to be backed up.
The Microsoft Windows certificate store contains the SSL server certificate used to secure communications with MOVEit Automation clients. If you are using client certificates , S/MIME or AS1/AS2/AS3, the Windows store also contains the related certificates.
To create a backup of the client certificates, run a MOVEit Automation task that uses the Certs Backup script.
It is less important to back up the MOVEit Automation SSL server certificate used to protect MOVEit Automation Admin and MOVEit Automation API connections because a new server certificate can be created by doing a fresh install.
Registry items to be backed up:
The registry is typically not changed often, so occasional backups should be sufficient.
Configuration Aging
Each time MOVEit Automation successfully saves a copy of its XML-based configuration files (miccfg.xml, etc.), it also ages up to four older versions in a simple grandfather scheme. For example, the "three saves ago" file is titled "miccfg.OL3".
If one of these files gets corrupted (often by an over-zealous anti-virus or backup utility), it is often possible to restore MOVEit Automation to a close-to-current state by copying one of the aged copies over the appropriate configuration file. For more information, contact MOVEit support.