Performing database replication failover - BlueCat Integrity - 26.1.0

Address Manager Administration Guide
ft:locale
en-US
Product name
BlueCat Integrity
Version
26.1.0

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 perform any administrative action (such as updating or changing the CLI configuration, rebooting, and so on) on the Primary or Standby servers. Such changes will affect BAM functionality and 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 Forcibly resetting database replication.

To perform a database replication failover:

  1. Log in to the UI of the Primary server.
  2. Select the Settings tab in the sidebar.
  3. Under Database management, select Replication settings.
  4. Click the ellipses within the row of the Standby server that you would like to promote to Primary and select Make primary.
  5. Select the Force failover replication check box to force the failover of replication to the selected Standby server. When deselected, the Primary server waits for any in-progress deployments to complete before initiating the failover to the Standby server.

    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, select the Force failover replication to ignore the latency value and perform the failover immediately.

    Attention: Selecting the Force failover replication check box overrides any in-progress deployments and can result in deployment errors.
  6. Click Make primary.
If you have previously had database backup configured, ensure that you enable database backup on the new primary server, and disable database backup on the new secondary server. For more information, refer to Database backup.