Migrating the configuration
You can back up the configuration of one FortiManager and then use the GUI or CLI to migrate the settings to another FortiManager on the same or different platform or version.
If you encrypted the FortiManager configuration file when you created it, you need the password to decrypt the configuration file when you migrate the file to another FortiManager model.
When migrating the database from another platform, all configurations except the system settings are migrated. These system settings must be manually copied from the original FortiManager model to the other FortiManager model. |
To migrate the FortiManager configuration using the GUI:
- In one FortiManager model, go to Dashboard.
- Back up the system. See Backing up the system.
- In the other FortiManager model, go to Dashboard.
-
If the configuration file is for multiple ADOMs, enable Administrative Domains in the System Information widget before migrating.
-
Click on the Restore option next to System Configuration.
The Restore System dialog appears. - Enable the option to Migrate from a different platform.
- Upload the backup file from the migrating platform, and click OK.
- After migrating, update the system settings, as needed.
-
Re-establish the FGFM tunnels. See Appendix C - Re-establishing the FGFM tunnel after VM license migration.
To migrate the FortiManager configuration using the CLI:
- In one FortiManager model, go to Dashboard.
- Back up the system. See Backing up the system.
- In the other FortiManager model, go to Dashboard.
-
If the configuration file is for multiple ADOMs, enable Administrative Domains in the System Information widget before migrating.
- Open the CLI Console, and enter the following command:
execute migrate all-settings <ftp | scp | sftp> <server> <filepath> <user> <password> <cryptpasswd>
-
After migrating, update the system settings, as needed.
-
Re-establish the FGFM tunnels. See Appendix C - Re-establishing the FGFM tunnel after VM license migration.
If the original FortiManager has databases from FortiGuard (antivirus, antispam, webfilter, etc.), they will not be included in the configuration file. After migrating, export the packages from the original FortiManager and import them to the other FortiManager. For example, see Exporting web filter databases example and Importing web filter databases example. |