Reset Replication Scenarios - BlueCat Address Manager - 9.0.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.0.0

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, where the latency has exceeded the configured critical threshold or the disk space on the Primary server is being exhausted, 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 servers 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 you have two Standby servers in replication and you have latency issues with one of the Standby servers, where the latency has exceeded the configured critical threshold or the disk space on the Primary server is being exhausted, remove the Standby server that cannot be contacted. For more information, refer to Modifying database replication from the user interface.

If the connection between the Primary server and all Standby servers is lost, you must 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 database and press ENTER. The Proteus prompt changes.
  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.

Note: After resetting replication, BlueCat recommends performing a full deployment to all managed DNS/DHCP Servers.

Case 2—Disaster Recovery Case

If the Primary server goes offline due to unexpected reasons, such as a result of physical damage or mechanical issues that cause it to become unusable, you must reset replication on the Standby servers depending on how many Address Manager servers you have in your database replication system.
Attention: BlueCat strongly recommends resetting replication on Standby servers only when the Primary server is offline or not functioning. Resetting replication on a Standby server when the Primary server is online can cause conflicts as both Primary and Standby servers have the ability to control the DNS/DHCP Server infrastructure.

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 database and press ENTER. The Proteus prompt changes.
  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.

    Note: After resetting replication, BlueCat recommends performing a full deployment to all managed DNS/DHCP 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 database and press ENTER. The Proteus prompt changes.
  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 database and press ENTER. The Proteus prompt changes.
  6. Type reset replication and press ENTER.
  7. Grant access to the new primary database on the remaining standby server.
  8. Log in to the Address Manager user interface 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.

Note: After resetting replication, BlueCat recommends performing a full deployment to all managed DNS/DHCP Servers.