Synchronize Environments

Overview

This guide describes how to synchronize two Bloomreach Content environments, referred to as S (source) and T (target), so that the target environment matches the state of the source.

When to Use

Synchronize environments when you need the target environment to reflect the current state of the source. A common scenario is updating a test environment to match production before performing upgrade tests or other validation.

Synchronization Strategy

To synchronize environment T with environment S, back up the database from S and restore it in T. This process ensures that all content and configuration from S are present in T.

Prerequisites

Access to both source and target environments
Permission to perform database backup and restore operations
Access to the CMS Console in both environments
Ability to stop and start CMS instances in the target environment

Steps

Back up the source database
Create a backup of the database in the source environment (S).
Refer to Backup and Restore Strategy for details.
You do not need to stop Bloomreach Content instances in S during backup.
Export environment-specific configuration from the target
In the target environment (T), use the CMS Console to export the following nodes and any other configuration that must be preserved:
```
/hippo:configuration/hippo:users
/hst:hst/hst:hosts
/targeting:targeting/targeting:datastores
/hippo:configuration/hippo:groups
/hippo:configuration/hippo:domains/everywhere/hippo:authrole
```
Export any additional nodes that contain environment-specific data you want to retain.
Stop CMS instances in the target environment
Shut down all Hippo CMS instances running in the target environment (T).
Remove the Jackrabbit index in the target
Delete the Jackrabbit index directory in T.
The default index folder location is:
```
${catalina.base}/../repository/workspaces/default/index
```
Restore the source database in the target environment
Import the previously backed up database from S into T.
Follow the instructions in Backup and Restore Strategy.
Truncate repository tables in the target database
In the target database, truncate the following tables:
```
REPOSITORY_LOCAL_REVISIONS
REPOSITORY_JOURNAL
```
Start the CMS in the target environment
Start the CMS in T and wait for the repository to complete indexing.
Restore exported nodes in the target
Use the CMS Console in T to import the nodes you exported in step 2.

Verification

Confirm that the target environment (T) contains all content and configuration from the source (S).
Verify that environment-specific users, groups, hosts, and other preserved nodes are restored correctly.
Ensure the CMS starts without errors and the repository is fully indexed.