How to perform database replication failover.
If you need to perform maintenance work on the Primary server and want another server
to temporarily maintain the Primary database, you can perform a failover. The
failover process promotes a selected Standby server to the Primary role, and
converts the current Primary server to a Standby role. During the failover process,
the database retains all committed transactions and becomes available in a stable,
known, good state.
Note:
- You must be an Address Manager Administrator to perform database replication failover.
- To perform a failover, the Primary database must be online. If the Primary server is offline, the Primary database isn't available, so you can't log in to the Address Manager web interface on the Standby servers.
Important: While database replication failover is in progress,
do not update or change the CLI configuration on Primary or Standby
servers. This will cause replication failover to fail.
If the Primary server isn't online, use the reset replication Administration Console command on the Standby server or servers. For more information, refer to Resetting database replication.
To perform a database replication failover: