Reset replication scenarios - BlueCat Address Manager - 8.3.1

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
8.3.1

How you reset and re-establish database replication depends on the critical situations that you are experiencing and how many Address Manager servers you have in your database replication system.

For example, if you are experiencing a simple network communication failure between the Primary and Standby servers and both servers are active, then you may want to reset the replication on the primary server to return it to stand-alone operation.

However, if your Primary server is physically damaged or mechanically unusable, then you may need to reset the replication on the Standby server(s) to return it to stand-alone state and make it function as a Primary server until you replace or repair the Primary server.

In either case, if you are running multiple Standby servers, you need to reset replication on all Standby servers.

Case 1—Network communication failure

If the connection between the Primary server and Standby server(s) is lost and both are active, you need to reset replication on the Primary server so that the replication can be disabled and the Primary server performs in a stand-alone state until you solve the issue.

  1. Log in to the Administration Console on the Primary server.
  2. From Main Session mode, type configure additional and press ENTER.
  3. Type reset replication and press ENTER.

    The primary server returns to a stand-alone service. You can now re-establish database replication between the primary and standby servers.

Case 2—Break in WAL file accumulation

When the total size of WAL files reaches the maximum allowable replication break threshold size, Address Manager creates the replication_break file in the /data/pgdata directory and breaks replication. When this occurs, you need to reset replication to establish database replication again.

  1. Log in to the Administration Console on the original primary server.
  2. From Main Session mode, type configure additional and press ENTER.
  3. Type reset replication and press ENTER.
  4. Re-create replication using Address Manager. For more information, refer to Configuring database replication.

Case 3—Disaster Recovery Case

If the Primary server goes offline due to unexpected reasons, you need to reset replication on the Standby server(s) depending on how many Address Manager servers you have in your database replication system.

If you have a single Standby server and the Primary server goes offline, perform the following:

Single Standby Server:

  1. Log in to the Administration Console on the Standby server.
  2. From Main Session mode, type configure additional and press ENTER.
  3. Type reset replication and press ENTER.

    The server returns to service and uses its copy of the replicated database. When the Primary server is returned to service, you can re-establish database replication between the two servers.

Two Standby Servers:

If you have two Standby servers and the Primary server goes offline, perform the following:

  1. Log in to the Administration Console on the first Standby server.
  2. From Main Session mode, type configure additional and press ENTER.
  3. Type reset replication and press ENTER.
  4. Log in to the Administration Console on the second Standby server.
  5. From Main Session mode, type configure additional and press ENTER.
  6. Type reset replication and press ENTER.
  7. Grant access to the new primary database on the remaining standby server.
  8. Log in to Address Manager on the server that you want to become the new Primary server.
  9. Configure database replication between the new Primary and Standby servers.

The servers return to service and use the replicated database from the new Primary server. When the original Primary server is returned to service, you can add the server to the database replication configuration.