Replication Control Panel - BloomReach Experience - Open Source CMS

This article covers a Hippo CMS version 12. There's an updated version available that covers our most recent release.

07-07-2017

Replication Control Panel

The administration perspective in the CMS contains a control panel for replication. Here you can monitor the status of the replication process, view error messages, pause and resume replication, and initiate a full or partial sync.

Initiating a full sync

When you first deploy your project, the target must be brought in sync with the source. The amount of time this takes depends heavily on the amount of data to be transferred. During a sync, regular replication processing based on changes to the repository is suspended. After the sync has completed, regular replication processing is resumed and the backlog of changes built up in the meantime is processed.

Running a partial sync

When for whatever reason it happens that some document or folder in the target becomes out of sync with the source you can always run a partial sync on that document or folder to bring it back in sync. Under normal circumstances this should never occur though. Enter the path to the node to be re-synced and click the button to initiate the partial sync. As in the case of a full sync, this will also suspend regular replication processing until the partial sync has completed.

Pausing/resuming replication

When you bring the target down for maintenance, or you have not yet set up your target, you may want to suspend the replication process for the time being, although in the former case this is not strictly necessary. The replication process monitors the status of the target and recovers from occurrences where it is down or unreachable. After the target has been brought up you can enable the replication process again. Replication will process the backlog of changes to be brought in sync automatically.

Monitoring error messages

When the source cannot reach the target due to the target being down or because of a severed network connection, error messages will be shown indicating the problem. Other error conditions are also reported in this way and may be monitored by an administrator. The replication engine can recover from some of these error conditions automatically. When that happens, a successful recovery is indicated by flagging the error message as fixed. Currently the only error condition from which replication engine knows how to automatically recover is when an ancestor of a unit of replication is reported missing on the target. In that case a partial sync rooted at the missing ancestor is automatically scheduled.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?