You are here: System Settings > Maintenance > Backup and Restore

Backup and Restore

The Backup feature allows you to back up an FortiADC’s user-configured objects and parameters to a file that can be uploaded and later restored to another FortiADC. Backup files may be uploaded to an FTP site or saved locally.

The Restore feature allows you to restored a previous backup file containing user-configured objects and parameters to another FortiADC. Restored files may be uploaded to an FortiADC through FTP or from a locally saved backup file.

On boot, FortiADC looks for a unique local peer definition in the configuration file by comparing the System ID found in each peer definition to all available licenses:

If a unique local peer definition is found, the System ID found in the local peer definition is compared against the System ID being used by the running system. If they do not match (as in the case where a backup file from one FortiADC is being restored on another FortiADC), the configuration file is modified to reflect the System ID of the running system and the signature is re-generated. If they do match, the configuration is not modified.

If a unique local peer definition is not found, then all peer definitions are removed from the configuration file and a new local peer definition is generated. This behavior is the same behavior that occurs if FortiADC is booted and there are no peer definitions found in the configuration file (which happens, for example, when the system is reset to factory defaults).

Restore features are available through the GUI and through eqcli.

Restore Notes

  1. eqcli restore of a backup archive from a local directory is not supported.
  2. When restoring a backup archive created on an FortiADC other than the one you are restoring, all IP addresses (clusters, servers, failover IP addresses, VLAN IP addresses, etc.) will be instantiated as-is from the backup archive. Consequently, if the unit on which the backup archive was created is connected to the network, IP conflicts will arise. You must correct the IP address conflicts before configuring the restored unit into failover, or issues (such as core dumps) will occur.
  3. If a backup was performed on a system with more interfaces than exist on the system on which it is being restored, full connectivity will not be restored if a VLAN specifies a port that does not exist on the system on which it is being restored. Connectivity can only be restored for vlans that specify ports that exist on the system on which they are being restored.
  4. When a backup is restored on a system: -- Any valid licenses present on that system are preserved. The licenses in the backup file are discarded. If there are no valid licenses on that system, the licenses in the backup file are restored.

Backup

The Backup feature allows you to back up an FortiADC’s user-configured objects and parameters to a file that can be uploaded and later restored to another FortiADC. Backup files may be uploaded to an FTP site or saved locally. Backup features are available through the GUI and through eqcli.

Note – eqcli backup of an archive to a local directory is not supported.
CollapsedBackup (GUI)
Collapsed Backup (CLI)

Restore

The Restore feature allows you to restored a previous backup file containing user-configured objects and parameters to another FortiADC. Restored files may be uploaded to an FortiADC through FTP or from a locally saved backup file.

On boot, FortiADC looks for a unique local peer definition in the configuration file by comparing the System ID found in each peer definition to all available licenses:

If a unique local peer definition is found, the System ID found in the local peer definition is compared against the System ID being used by the running system. If they do not match (as in the case where a backup file from one FortiADC is being restored on another FortiADC), the configuration file is modified to reflect the System ID of the running system and the signature is re-generated. If they do match, the configuration is not modified.

If a unique local peer definition is not found, then all peer definitions are removed from the configuration file and a new local peer definition is generated. This behavior is the same behavior that occurs if FortiADC is booted and there are no peer definitions found in the configuration file (which happens, for example, when the system is reset to factory defaults).

Restore features are available through the GUI and through eqcli.

Restore Notes

  1. eqcli restore of a backup archive from a local directory is not supported.
  2. When restoring a backup archive created on an FortiADC other than the one you are restoring, all IP addresses (clusters, servers, failover IP addresses, VLAN IP addresses, etc.) will be instantiated as-is from the backup archive. Consequently, if the unit on which the backup archive was created is connected to the network, IP conflicts will arise. You must correct the IP address conflicts before configuring the restored unit into failover, or issues (such as core dumps) will occur.
  3. If a backup was performed on a system with more interfaces than exist on the system on which it is being restored, full connectivity will not be restored if a VLAN specifies a port that does not exist on the system on which it is being restored. Connectivity can only be restored for vlans that specify ports that exist on the system on which they are being restored.
  4. When a backup is restored on a system: -- Any valid licenses present on that system are preserved. The licenses in the backup file are discarded. If there are no valid licenses on that system, the licenses in the backup file are restored.
CollapsedRestore (GUI)
CollapsedRestore (CLI)