Data Replication

Data replication copies data, metadata, and files from staging to either the development or production instance.

Note: You can't use replication to populate a developer sandbox with data from staging. Instead, export data from staging and then import it to the sandbox.

Data replication functions at two levels: global replication, which includes configuration information and data that applies to your entire organization, and site replication, which includes data belonging to one or more specified sites (such as product and catalog data, XML-based content components, and image files). When you create a new PIG, you must run a full global replication to each target instance before running any site replications to it.

After the initial global replication, you can configure which data is included in subsequent replications by selecting specific replication tasks, and can combine global and site-level data in a single process. Review the tasks to understand the granularity at which different types of data are replicated. For example, you can replicate a single catalog, but you can't replicate only a specific product. Partial data replication is useful in cases such as the following.

When you replicate data, the data you select replaces the corresponding data on the target instance. For example, your staging and development instances both include catalogs A, B, and C. On your staging instance, you update catalog B, delete catalog C, and add catalog D. When you replicate catalogs from staging to development, on your development instance catalog A is unaffected, catalog B is updated, catalog C is deleted, and catalog D is added.

Note: Only the data selected for replication is overwritten on the target instance. Other data is not affected. In the previous example, if you replicate data other than catalogs from staging to development, then catalogs A, B, and C remain unaffected on the development instance, and catalog D is not added.

What Data Replication Does not Include

You can't replicate the following data. Instead, create or import it in development and production instances.

Data Replication Process Types

Data replication is a two-step process. First, data is transferred from staging to the target instance, then it is published on the target instance. You can run both steps as a single replication process, or run them separately. Running them separately can help you identify the source of failures that might occur.

There are four types of data replication processes.

Note: You run all replication processes on the staging instance, even Publishing and Undo, which only affect the target instance.
Replication Type Description
Transfer The selected data on the source instance is transferred to the target instance, but does not replace or affect the current data on the target. You must then run a replication process of type Publishing to update the target instance data.
Transfer & Publishing The selected data on the source instance is replicated to the target instance and immediately replaces the existing data.
Publishing This process is available only after a successful Transfer process. Publishing replaces the existing data on the target instance with the previously transferred data. The replication tasks in the Publishing process must exactly match the tasks in the Transfer process. You cannot transfer data and then publish only some of it. If any of the transferred data no longer exists on the target, then the replication process fails.
Note: You must disable incremental indexing when you run a Publishing replication process.
Undo This process is available only after a successful Transfer & Publishing or Publishing replication process. It reverts the target instance to the data that existed there before the last replication process.

Related Links


Create a Data Replication Process

Verify a Data Replication

Data Replication Tasks

Replication Best Practices