Fortinet Document Library

Version:

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Recovery

If high availability has been implemented and a failover has occurred, you must correct the reason for the failover before restarting your Primary Server.

Restart the primary server

Use the Resume Control button on the Dashboard Summary panel to start the primary again. When the Resume Control button is clicked, critical files are copied from the secondary back to the primary and control is returned to the primary. On the (Undefined variable: User_Guide.ProductAbbrev) Server, (Undefined variable: User_Guide.ProductAbbrev) Control Server and FortiNAC Control Manager appliances, the database is also copied.

If you are using high availability for a (Undefined variable: User_Guide.ProductAbbrev) Control Server and Application Server pair and this configuration does not use a shared IP address, when failover occurs both servers failover. To return control to the primary pair, click the Resume Control button on the Dashboard Summary panel for either of the two servers in the pair. This causes both the (Undefined variable: User_Guide.ProductAbbrev) Control Server and Application Server in the primary pair to start again and control is returned to both servers in the primary pair.

Note

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

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

This process may take a few moments while the data is synchronized between the two servers.

Manually restart, stop or force a failover

The scripts in the table below allow you to control High Availability from the CLI. Scripts to restart the primary servers vary depending on the configuration implemented. For configuration options see Primary and secondary configuration.

CLI scripts

Server Type

Primary Recovery

Shutdown Without Failover

Shutdown With Failover

Shared IP address

(Undefined variable: User_Guide.ProductAbbrev) Server

(Undefined variable: User_Guide.ProductAbbrev) Control Server

FortiNAC Control Manager

hsRestartCMMaster

shutdownCampusMgr

shutdownCampusMgr -kill

(Undefined variable: User_Guide.ProductAbbrev) Application Server

hsRestartCMRCMaster

shutdownNessus

shutdownNessus -kill

No shared IP address

(Undefined variable: User_Guide.ProductAbbrev) Control Server

hsRestartPair

(restarts both servers in the pair)

shutdownCampusMgr

shutdownCampusMgr -kill

(Undefined variable: User_Guide.ProductAbbrev) Application Server

hsRestartPair

(restarts both servers in the pair)

shutdownNessus

shutdownNessus -kill

Recovery

If high availability has been implemented and a failover has occurred, you must correct the reason for the failover before restarting your Primary Server.

Restart the primary server

Use the Resume Control button on the Dashboard Summary panel to start the primary again. When the Resume Control button is clicked, critical files are copied from the secondary back to the primary and control is returned to the primary. On the (Undefined variable: User_Guide.ProductAbbrev) Server, (Undefined variable: User_Guide.ProductAbbrev) Control Server and FortiNAC Control Manager appliances, the database is also copied.

If you are using high availability for a (Undefined variable: User_Guide.ProductAbbrev) Control Server and Application Server pair and this configuration does not use a shared IP address, when failover occurs both servers failover. To return control to the primary pair, click the Resume Control button on the Dashboard Summary panel for either of the two servers in the pair. This causes both the (Undefined variable: User_Guide.ProductAbbrev) Control Server and Application Server in the primary pair to start again and control is returned to both servers in the primary pair.

Note

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

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

This process may take a few moments while the data is synchronized between the two servers.

Manually restart, stop or force a failover

The scripts in the table below allow you to control High Availability from the CLI. Scripts to restart the primary servers vary depending on the configuration implemented. For configuration options see Primary and secondary configuration.

CLI scripts

Server Type

Primary Recovery

Shutdown Without Failover

Shutdown With Failover

Shared IP address

(Undefined variable: User_Guide.ProductAbbrev) Server

(Undefined variable: User_Guide.ProductAbbrev) Control Server

FortiNAC Control Manager

hsRestartCMMaster

shutdownCampusMgr

shutdownCampusMgr -kill

(Undefined variable: User_Guide.ProductAbbrev) Application Server

hsRestartCMRCMaster

shutdownNessus

shutdownNessus -kill

No shared IP address

(Undefined variable: User_Guide.ProductAbbrev) Control Server

hsRestartPair

(restarts both servers in the pair)

shutdownCampusMgr

shutdownCampusMgr -kill

(Undefined variable: User_Guide.ProductAbbrev) Application Server

hsRestartPair

(restarts both servers in the pair)

shutdownNessus

shutdownNessus -kill