Fortinet black logo
7.2.0

Recovery

Recovery

If High Availability (HA) has been implemented and a failover has occurred, correct the reason for the failover. Once corrected, resume control of the Primary Server(s).

Important: Resuming control is not an automatic process and must be done manually.

Restart The Primary Server

Under normal operation, the Resume Control button on the Dashboard System Summary widget is grayed out. Once a failover has occurred, this button becomes enabled. Use the Resume Control button to initiate the process of transitioning control from the Secondary Server(s) back to the Primary Server(s). The database is also copied.

  1. Navigate to Bookmarks > Dashboard.

  2. Scroll to the Summary panel.

  3. Click the Resume Control button for the server that should resume control.

  4. The Primary Server restarts. Database and configuration files are copied from the secondary to the primary. Processes are started on the primary. Then the Secondary Server relinquishes control.

Note: If for any reason the database was not replicated correctly on the secondary before failover, the recovery process gives the option of retaining the older database located on the primary.

Recovery

If High Availability (HA) has been implemented and a failover has occurred, correct the reason for the failover. Once corrected, resume control of the Primary Server(s).

Important: Resuming control is not an automatic process and must be done manually.

Restart The Primary Server

Under normal operation, the Resume Control button on the Dashboard System Summary widget is grayed out. Once a failover has occurred, this button becomes enabled. Use the Resume Control button to initiate the process of transitioning control from the Secondary Server(s) back to the Primary Server(s). The database is also copied.

  1. Navigate to Bookmarks > Dashboard.

  2. Scroll to the Summary panel.

  3. Click the Resume Control button for the server that should resume control.

  4. The Primary Server restarts. Database and configuration files are copied from the secondary to the primary. Processes are started on the primary. Then the Secondary Server relinquishes control.

Note: If for any reason the database was not replicated correctly on the secondary before failover, the recovery process gives the option of retaining the older database located on the primary.