How to configure database replication.
Note: You must establish a trust relationship between the Address Manager servers you wish to be in replication prior to configuring database replication in Address Manager. For more information about establishing Trust Relationships, refer to Configuring a Trust Relationship in Address Manager.
Database Replication is supported between the following Address Manager disaster recovery systems:
- 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
Before configuring database replication, make sure to complete the following prerequisites:
- The user configuring database replication has administrator privileges
- Ports 22, 443, 873, 1099, and 5432 are open on the firewall between the affected Address Manager appliances and/or virtual machines.
- 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.
- Do not place any files in the /data/pgdata directory of the Address Manager servers. This will cause replication failure.
- When database replication is configured, you MUST ONLY perform actions from the Primary server. You must not perform any updates, changes, or deployments from the Standby server.
- 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.
Attention: BlueCat strongly advises customers using Address Manager in replication to secure the communication channel between the Primary and Secondary (or Tertiary) servers, for example by using a VPN between data centers.