Use replication to safely move new and updated storefront data and code between instances on your Primary Instance Group (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.
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 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.
Be sure to consider our recommended best practices when configuring 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.