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
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. |
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