What happens to the backup device after the initial HA sync is completed?

After the initial High Availability (HA) synchronization is completed, the backup device automatically reboots and rebuilds its log database. This process ensures that the backup device has the latest configuration and log information from the primary device, allowing it to take over seamlessly in case of a failure of the primary device.

Once the HA sync is accomplished, the backup device's reboot is essential for applying the changes and ensuring that it is fully operational and in sync with the primary device's configuration and logs. This rebuilding of the log database is a crucial step, as it prepares the backup device to maintain continuity in logging and configuration should it need to become active.

Other options, while potentially relevant in different contexts, do not accurately represent the actions of the backup device after the initial HA sync. For instance, the backup device does not simply remain inactive without activation or require a complete reconfiguration, as these would not reflect the efficiency and robustness of the HA system designed by Fortinet. Additionally, real-time synchronization is not the primary action taken after the initial sync; rather, the reboot and log database rebuilding are designed to reinforce the HA setup's reliability and readiness for any failover situation.