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.
- 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.
- Under Database Management, click Database Management.
- Click Database Replication.
- Click the Database Replication menu and select Configure.
Under Configure Database 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.
- Compression—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 (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.Note: To establish database replication again, refer to Resetting database replication.
- 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.Note: To establish database replication again, refer to Resetting database replication.
- 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 IPv4 or IPv6 address of the first Standby server. Click Remove to remove the Standby server.
- Standby Server 2 (Optional)—displays the IPv4 or
IPv6 address of the second Standby server if a second Standby server has
been configured. Click Remove to remove the Standby server.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.
Warning: When you confirm changes to the database replication settings, the existing database on the Standby servers will be erased.
- Click Confirm.
- Click OK.
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.