Snapshots
A snapshot is a .zip file that contains all relevant data describing the state of a Conductor Manager the moment the snapshot is created on this Manager. There are four basic operations associated with snapshots: creating, downloading, uploading and restoring. For detailed information about snapshot-related CLI commands, click here.
Common use cases for snapshots are:
- Backing up the Manager to be able to restore its state later on, should it become inconsistent or broken for whatever reason. Note that if you attempt to restore after losing an old manager you will need to have the same IP assigned to the new manager or the restore process will likely require support.
- Migrating to a newer Conductor Manager version, by creating a snapshot on the old manager and restoring it on the new one.
In this case, if you have any installed deployments, you also need to execute the install_new_agents workflow on the new Conductor Manager so that all hosts agents are updated and connected to RabbitMQ on the new Conductor Manager.
Snapshots are security-sensitive. SSL certificates, hash salts, credentials, and other sensitive information regarding your environment are likely to be stored in snapshots.
A snapshot can only be successfully restored to a clean Conductor Manager, meaning newly-created and without blueprints or deployments.
If you attempt to restore a snapshot to a Conductor Manager that is not clean, the operation may be prevented, and will be unsuccessful.
During any snapshot restore process where it is possible to do so, the old manager should be kept online throughout the process..
Using the Conductor Management Console
Snapshot management is performed via the Snapshots page in the Conductor Management Console. You must have admin credentials to create and restore snapshots.