Use replication to safely move new and updated storefront data and code between instances on your Primary Instance Group (PIG).

Note: You can only run replication on a Primary Instance Group (PIG)—not on a Secondary Instance Group (SIG). Use code deployment to move code from a sandbox instance on your SIG to a staging instance on your PIG.

Replication pushes data or code from a staging instance to a development or production instance. First, replicate to a development instance to verify the replication and check functionality. After testing the development instance, make any necessary changes on your staging instance and repeat the process. When everything is ready, replicate from staging to production.

Replication Processes

A replication process is a collection of replication tasks that control which data or code is pushed to the replication target instance. You manage data and code replication processes in Business Manager by selecting Administration > Replication on the staging instance.

The main data or code replication page displays basic information about each existing process. You can select the ID of a process to open its details, or select the replication type of a process to expand a list of its replication tasks. When viewing the details of a process that is in the Waiting state, you can edit it by clicking Edit.

When you configure a data or code replication process, you can run it immediately, schedule it to run at a later time, or assign it to be run by a job. You can also set up data replication processes (only) to recur daily, weekly, or monthly at a specific time.

Do not make manual edits in Business Manager on either the source or target instance while replication is running. Also, make sure that no jobs are running on the target instance during replication.

Note: When you schedule a replication process to run at a later time, it replicates the system state at the time it runs, not the state from the time when it was created.
Note: If a recurring data replication process fails, it will not run again.

Be sure to consider our recommended best practices when configuring replication.

Rolling Back a Replication

You can undo a replication by running another replication with the Replication Type set to Undo. This restores the target instance to its previous state.

Note: Only the most recent data or code replication can be rolled back. You can't undo a replication and then undo the previous replication. However, data and code replications do not affect each other's rollbacks. For example, if you run a data replication and then a code replication, you can still undo the data replication, and vice versa.

Related Links

Data Replication

Code Replication

Data Replication Tasks

Replication Best Practices

Troubleshooting Replication

Page Cache and Replication

Code Deployment