Category: Backup usage
Context: Command-Line Interface
There are two separate use cases for restoring FireMon backups: to recover to an earlier point in time, or to migrate data to another system.
A recovery simply restores the data on the machine to its state from when the backup was created. A recovery can be performed by restoring a backup file on the machine where it was created. When performing a recovery, all three parts of the backup are restored, including the FMOS System Configuration.
Consider using a recovery restore when:
The destination machine is the same as the origin machine OR
The destination machine has the same SIP roles as the origin machine
A migration transfers data from one system to another. This is done, for example, to copy data from a production environment to a testing environment, or to move data to a new machine. When performing a migration, the database and filesystem contents are restored, but not the FMOS System Configuration.
Starting with FMOS 9.7.0, migration is the default restore mode.
Consider using a migration restore when:
The destination machine is NOT the same as the AND origin machine is still running OR
The destination machine has different SIP roles than the origin machine OR
The destination machine is in a different environment than the origin machine
When performing a migration in a distributed deployment, the backup MUST be restored before any application server machines are added to the ecosystem. If AS machines have already joined, they will have to be reset to factory defaults, reconfigured, and added to the ecosystem again after the restore completes.