solidDB Help : High availability : solidDB HotStandby : High Availability Controller : Failure handling with High Availability Controller (HAC) : Primary server (or computer) fails
  
Primary server (or computer) fails
Scenario
Server #1 (in PRIMARY ACTIVE state) on Node A fails (or Node A fails).
Server #2 (in SECONDARY ACTIVE state) on Node B registers the connection failure to Server #1.
Recovery
To recover from the primary server failure the secondary server replaces the primary server. The recovery proceeds automatically as described in the following table:
 
Description
Illustration
The secondary server (Server #2) fails to connect to the primary server (Server #1) and Server #2 switches to SECONDARY ALONE state automatically.
This diagram is described in the first column of the row
The HAC instance on Node B concludes that the primary server has failed and switches Server #2 to PRIMARY ALONE state.
Applications access data from Server #2 (new primary server).
Server #2 saves all transactions in the transaction log.
At the same time, the HAC instance on Node A restarts Server #1 in SECONDARY ALONE state.
Note If Node A failed rather than just Server #1, Node A and the HAC instance on Node A must be restarted before the HAC instance can restart Server #1.
This diagram is described in the first column of the row
The HAC instance on Node B connects the primary and secondary servers.
Server #1 reads and applies any outstanding transactions from the transaction log on Server #2.
Note If the HAC cannot connect the servers, the HAC can be configured to initiate a NETCOPY operation to synchronize Server #1 with Server #2.
This diagram is described in the first column of the row
Go up to
Failure handling with High Availability Controller (HAC)