How to configure database replication.
- identical Address Manager appliances models, such as two Address Manager 3000 appliances
- identical Address Manager virtual machines, such as two Address Manager 3000 VMs
- matching Address Manager appliances and virtual machines, such as an Address Manager 3000 appliance and Address Manager 3000 VM
- The user configuring replication has administrator privileges.
- Ports 22, 80, 443, 1099, and
5432 are open on the firewall between the affected Address
Manager appliances or virtual machines. For more information on service
ports, protocols, and usage, refer to Address Manager service ports.
Note: Address Manager uses port 80 and 443 for bidirectional communication between the Primary and Secondary servers.
- ICMP (Internet Control Message Protocol) is enabled on all Address Manager servers in replication. This allows the Primary to reach the Secondary and Tertiary servers.
- The database version MUST match the current version of the Address Manager software.
- The Address Manager servers to be configured with database replication must
have matching IP address configurations. For example, all Address Manager
servers must all be configured with IPv4 addresses only, IPv6 addresses
only, or in dual-stack with IPv4 and IPv6 addresses.Attention: If you have database replication configured with mixed IP configurations, such as an Address Manager server with IPv4 only addresses in replication with an Address Manager server with IPv4 and IPv6 addresses in dual-stack, the secondary Address Manager server will no longer be in replication upon upgrading to Address Manager v9.4.0.
If your secondary Address Managers are no longer in replication after upgrading to Address Manager v9.4.0, you must reconfigure the secondary Address Manager so that the IP address configuration matches the configuration of the primary Address Manager (IPv4 only, IPv6 only, or dual-stack) and re-enable replication.
- Do not place any files in the /data/pgdata directory of the Address Manager servers. This will cause replication failure.
- While database replication is in progress, don't update or change the CLI configuration on Primary or Standby servers. This will cause replication failure.
- While database replication is in progress, UI access on the Standby server will fail if the JMX passwords differ on the Primary and Standby servers. For instructions on setting the JMX password, refer to Setting the JMX password.
- When database replication is configured, you can only migrate data into the Primary server and not into any Standby servers. The Migration link on the Administration page is only available from the Primary server in replication.
- When database replication is configured, you cannot perform a database
backup on the Standby servers; however, you can still configure a
disabled database backup profile on the Standby servers. If you attempt
to execute a database backup on a Standby server, the following error
System does not have a primary database. Backup [backup_name] cancelled