Bring back primary and standby nodes after both nodes fail by using the GUI

In this scenario, the primary node has failed and the standby node has taken over as the new primary node. Before a new backup can be powered on, the new primary node fails. You need to restart both nodes. System administrators can use the High Availability page in the Amlen WebUI.

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 Bring back primary and standby nodes after both nodes fail by using the command line. In this scenario, the content of the store and configuration of Appliance B is preserved.

  1. 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.
  2. Click Restart Later when prompted.
  3. Stop and then restart the Eclipse Amlen server for 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.