Bring back the last primary node after the primary and then the standby node fails by using the GUI

In this scenario, the primary node fails and the standby node takes over as the new primary node. Before a new backup can be setup, the new primary node fails. You must restart a new primary node and set up a new standby node. System administrators can use the High Availability page in the Amlen WebUI.

The two Eclipse Amlen appliances must be physically connected. For more information about connecting appliances, see Configuring the system for High Availability. The administrative state (AdminState) of the two appliances must also be enabled. Go to the Network Settings page to set the administrative state of the appliances.

You can configure appliances for high availability by using the Amlen WebUI, or by using the command line. For more information about using the command line to configure appliances for high availability, see Primary node fails then standby node fails, bring back last primary node by using the command line. In this scenario, the content of the store and configuration of Appliance B is preserved.


Primary node fails then backup fails, bring back last primary node
  1. Clean the store on Appliance C:
    1. Click System Control in the Appliance menu.
    2. Select maintenance from the Runmode list.
    3. Stop the server by clicking Stop the server.
    4. Start the server by clicking Start the server.
    5. Select the clean store check box.
    6. Stop the server by clicking Stop the server.
    7. Start the server by clicking Start the server.
    8. Select production from the Runmode list.
  2. Configure high availability on Appliance C:
    1. From the Appliance menu, select High Availability.
    2. Click Edit in the Configuration panel. The Edit High Availability Configuration page is displayed.
    3. Select the High Availability Enabled check box.
    4. Complete the High Availability Group field.
      The high availability group is used to automatically configure appliances to pair with each other. The value must match the value on Appliance B. When this value is set, you do not need to provide replication or discovery addresses.
    5. Click Save.
    6. Click Restart Later.
  3. Check the high availability configuration on Appliance B is correct by selecting High Availability from the Appliance menu. If you change any settings, click Save and then click Restart Later.
    Tip: It is recommended, but not required, to set Appliance B as the preferred primary node. To set Appliance B as the preferred primary node, select the When both nodes start in auto-detect mode, this node is the preferred primary node check box in the Advanced Settings section.
  4. Stop and then restart the Eclipse Amlen servers on both of the appliances:
    Tip: As a best practice, stop and restart the standby server first. Then stop and restart the primary to limit the amount of time that the primary spends waiting for the standby to become available.
    1. Click System Control in the Appliance menu.
    2. Stop the server by clicking Stop the server.
    3. Start the server by clicking Start the server.
When the HA pair is up and running, you can view the status of each appliance from the Status menu on the Amlen WebUI. You can view further information on the status of the appliance by using the System Control page. You can view further information about the high availability role of the appliance by using the High Availability page.