| Description | This article describes the expected behavior when using an automation stitch for an HA cluster. |
| Scope | FortiGate 7.0.x. |
| Solution |
It is expected to see 2 backup configurations on a server with the names appended from FortiGate primary and secondary units, which will append the Serial number_filename. HA environments copy the primary unit's configuration to the secondary, so any automation stitches/actions/triggers will exist on both FortiGates.
Example of the backup file generated:
The differences are mainly in the encrypted password and hostname. |
