Failover steps (explained)

Failover Service processesVer2

Involved servers (numbers in red):

  1. Recording server
  2. Failover recording server
  3. Management server.

Failover steps for Cold standby setups:

  1. To check whether it is running or not, a failover recording server has a non-stop TCP connection to a recording server.
  2. This connection is interrupted.
  3. The failover recording server requests the current configuration of the recording server from the management server. The management server sends the requested configuration, the failover recording server receives the configuration, starts up, and starts recording on behalf of the recording server.
  4. The failover recording server and the relevant camera(s) exchange video data.
  5. The failover recording server continually tries to re-establish connection to the recording server.
  6. When the connection to the recording server is re-established, the failover recording server shuts down and the recording server fetches video data (if any) recorded during its down-time and the video data is merged back in to the recording server database.

Failover steps for Hot standby setups:

  1. To check whether it is running or not, a hot standby server has a non-stop TCP connection to its assigned recording server.
  2. This connection is interrupted.
  3. From the management server, the hot standby server already knows the current configuration of its assigned recording server and starts recording on its behalf.
  4. The hot standby server and the relevant camera(s) exchange video data.
  5. The hot standby server continually tries to re-establish connection to the recording server.
  6. When the connection to the recording server is re-established and the hot standby server goes back to hot standby mode, the recording server fetches video data (if any) recorded during its down-time and the video data is merged back in to the recording server database.

© 2018 Milestone Systems A/S