Configuring database replication from the Address Manager user interface - BlueCat Integrity - 26.1.0

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

How to configure database replication.

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

To configure database replication:
Attention: You must establish a trust relationship between the Address Manager servers you wish to be in replication prior to configuring replication in Address Manager.
Note: If you previously established database replication and would like to configure database replication again, refer to Forcibly resetting database replication.
  1. Select the Settings tab in the sidebar.
  2. Under Database management, select Replication settings.
  3. Click Configure replication.
  4. Under Configure replication, set the following database replication parameters:
    • Primary Server—displays the IPv4 or IPv6 address for the server on which you are enabling database replication. This server becomes the Primary server.
    • Compress replication stream—select to compress the database replication stream. Use compression when you have concerns about the network bandwidth between the Primary server and the Standby server or servers.
      Attention: Compressing the database replication stream can be resource intensive. Using this option might affect performance.
    • Latency warning threshold—enter a value to specify the warning threshold latency1 of replication and set the Unit .

      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 1 hour.

      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—enter a value to specify the critical threshold latency of replication and set the Unit. 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 1 day.
    • Standby server 1—select a server to function as a Standby server. All Address Manager servers listed in the drop-down menu 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 2—(Optional) select the IPv4 or IPv6 address of the second Standby server if a second Standby server has been configured.
      Attention: When adding a Standby server, the server can't be part of an existing database replication environment or a Removed Standby server. You can only add a Standby server if it's operating as a standalone server.

      Both the Primary Server and any Standby Servers must have the same IP address availability. For example, if both IPv4 and IPv6 addresses are available on the Primary, both must be available on all Standbys. If only IPv4 addresses are available on the Primary, then only IPv4 addresses must be available on the Standby.

  5. Click Configure.
    Warning: When you confirm changes to the database replication settings, the existing database on the Standby servers will be erased.
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.