Modifying database replication from the user interface - BlueCat Address Manager - 9.0.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.0.0

How to modify database replication once it has been configured.

Configure settings for the Primary and Standby servers used in database replication.

To modify database replication:

  1. 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.
  2. Under Database Management, click Database Management. The Database Management page opens.
  3. Click Database Replication. The Database Replication page opens.
  4. Click the Database Replication menu and select Modify. The Modify Database Replication page opens.
  5. Under Configure Database Replication, set the following database replication parameters:
    • Primary Server—displays the IP address of the Primary server.
    • Compression—displays whether compression is enabled for the database replication stream.
      Note: You cannot enable or disable compression from the Modify Database Replication page.
    • Latency Warning Threshold (sec)—enter a value to specify the warning threshold latency1 of replication, in seconds. When the latency between the Primary and Standby servers reaches the configured threshold, Address Manager logs a warning in syslog and sends an event to warn you that the database of the Standby server is behind the database of the Primary server by the configured threshold or greater. The values for this field range between 0 seconds and 2500000 seconds; the default value is 3600 seconds.
      Note: If you set the value to 0 seconds, Address Manager will never send an event to warn you that the database of the Standby server is behind the database of the Primary server.
    • Latency Critical Threshold (sec)—enter a value to specify the critical threshold latency of replication, in seconds. When the latency between the Primary and Standby servers reaches the configured threshold, Address Manager logs a warning in syslog and sends an event to warn you that the database of the Standby server is behind the database of the Primary server by the configured threshold or greater. The default value is 86400 seconds.
    • Add Standby Server—select a server to function as a Standby server, then click Add. All Address Manager servers listed in the Add Standby Server field are in a trust relationship with the current server. The server selected is the first Standby server. Selecting an additional standby server adds a second Standby server.
    • Standby Server 1—displays the IP address of the first Standby server. Click Remove to remove the Standby server.
    • Standby Server 2—displays the IP address of the second Standby server if a second Standby server has been configured. Click Remove to remove the Standby server.
      Attention:
      • If you have two Standby servers in replication, you can only remove one Standby server. You must have at least one Standby server in replication.
      • If you are adding a second Standby server, the server cannot be part of an existing database replication environment or a Removed Standby server. You can only add a Standby server if it is operating as a Standalone server.
      Warning: If you are adding a second Standby server, the existing database on the new Standby server will be erased.
  6. Click Continue. The Modify Database Replication Confirmation page opens.
  7. Click Confirm.
  8. Click OK.
    Attention:
    • If you have added or removed a Standby server, BlueCat recommends performing a full deployment to all managed DNS/DHCP Servers.
    • If you have removed a Standby server from replication, you can re-purpose the server as a Standalone server. To re-purpose the server as a Standalone server, you must reset replication on the removed Standby server. For more information on resetting replication, refer to Resetting database replication.
1 The latency is the delay between the time that a particular update was performed on the Primary server and the time that it was committed on the Standby server.