Top
Enterprise Postgres 16 Cluster Operation Guide(Database Multiplexing)

5.9 Status Update after Failover

When Mirroring Controller performs a failover, standby instance will be promoted to standalone instance. The Mirroring Controller setup will be removed from both standby and master instances.

The following scenario describes one of the ways in which failover can be triggered, and the results achieved by the use of Mirroring Controller in WebAdmin.

  1. In the [Instances] tab, select the master instance "inst1".

  2. Click .

  3. In the confirmation dialog box, the warning "This instance is being monitored by Mirroring Controller. Stopping the instance may result in cluster failover." is displayed.

  4. Choose the stop mode and click [Yes].

    In the server, the following takes place:

    1. The master instance is stopped.

    2. Failover is triggered in Mirroring Controller.

    3. The Mirroring Controller setup is removed from both master and standby instances

    4. Standby instance is promoted to standalone.

  5. When the instance is refreshed in WebAdmin, the latest status of the instances will be displayed.

Note

When failover is performed, the Mirroring Controller setup is removed from both master and standby instances. Therefore, to manage the Mirroring Controller using WebAdmin again, create the standby instance and set up Mirroring Controller.

Refer to "Creating a Standby Instance" in the Operation Guide for details.

Refer to "5.1 Mirroring Controller Setup" for details.