How to perform database replication failover.
- 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.
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 Forcibly resetting database replication.
To perform a database replication failover:
- Select the Administration tab. Tabs remember the page on which you last worked, so select the Administration tab again to ensure you are working on the Administration page.
- Under Data Management, click Database Management.
- Click Database Replication.
- Click Database Replication and select Failover.
Under Select New Primary Server, select the new Primary
server from the New Primary Server drop-down menu.
The drop-down menu displays the IP address and latency of the Standby servers.
- Click Continue.
If the latency of the Standby server isn't 0, the Current latency for the target Primary server field appears and displays the latency of the Standby server that will become the new Primary server. The database replication failover occurs once the latency of the Standby server reduces to 0. If the latency doesn't reduce to 0 or the failover needs to be initiated immediately, click Force to ignore the latency value and perform the failover immediately.
Once the latency reduces to 0 or the Force button is clicked, the database replication failover initiates and the database replication status changes to "Failover is in progress".Note: Once a failover is in progress, navigating to the Database Replication page redirects you to the Failover progress page.