Salesforce B2C Commerce 24.7 > Administering Your Organization > Replication

Replication Processes

A replication process performs a replication or rolls back a previous replication. You can run a replication process manually, or schedule it to run automatically.

When using replication, first replicate from your staging instance to a development instance. Then, check the results on the development instance. If changes are needed, make them on your staging instance and repeat the process. When you have verified that everything is correct on the development instance, replicate from staging to production.

Note: You can only use replication on instances in your Primary Instance Group (PIG). To move code from a sandbox instance in your Secondary Instance Group (SIG) to a staging instance in your PIG, use code deployment.

Copying Data or Code

A replication process is a collection of replication tasks that push specified data or code to the target instance.

To manage replication processes in Business Manager, log into the staging instance and select Administration > Replication. The main data or code replication page displays basic information about each existing process. Select the ID of a process to open its details, or select its replication type 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.

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: A scheduled replication process replicates the current system state when it runs, not the state from the time when the process was created.

Note: If a recurring data replication process fails, it stops recurring.

Rolling Back a Code or Data Transfer

To roll back a replication and restore the target instance to its previous state, run another replication process with the Replication Type set to Undo.

Note: You can only roll back the single most recent data or code replication. For example, you can't undo a code replication and then undo the previous code 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.