Database Replication keeps a replica database in sync with a master database. Before you can configure database replication, you must first couple the local cluster together with a different (foreign) cluster. To couple clusters, go to the Clusters > Local Cluster page. You can configure the following on the Database Replication Configuration Page:
A Local Database is the database on this cluster.
A Foreign Cluster is another cluster to which this cluster communicates.
You can set up a Local Database to replicate to a Foreign Cluster or vice versa. You set whether the Local database is the master or the replica with the Local Database As radio buttons.
A Foreign Replica is a database on a Foreign Cluster to which this database replicates its content.
The Lag Limit is the amount of time, in seconds, that the replica database can lag behind the master database. The default is 15 seconds. Use caution setting it to a lower value, as it can slow down transactions on the master database (because if the limit is reached, then transactions on the master are stalled until the replica catches up).
The Connect Forests By Name setting specifies if forests on the master database are automatically mapped to forests with the same name on the replica database.
The Foreign Admin Interface Protocol setting specifies if the Admin Interface on the foreign cluster uses http or https.
The Foreign Admin Interface Port setting specifies the port on which the Admin Interface App Server runs on the foreign cluster.
The Host in Foreign Cluster setting specifies which host in the foreign cluster is used to communicate with this cluster.
The Foreign Cluster ID is the ID describing the cluster containing the replica database.
The Foreign Database ID is the ID of the database on the foreign cluster (that is, the ID of the replica database).
Connect Forests By Name specifies if the replica forests are set up to use forests of the same name as the forests in the master forest. If Connect Forests By Name is set to true, then replica forests that have the same name as forests attached to the master database will automatically be configured when they appear in the replica database, even if they do not exist at the time you are initially configuring the database. For example, if you attach a new forest to the database, and if you attach a new forest to the replica database with the same name, then that replica forest will automatically configure itself as the replica forest for the corresponding forest on the master database.
Buttons and Tabs: