Top-Up Extraction

The Content Transfer Tool has a feature that supports differential content top-up where it is possible to transfer only changes made since the previous content transfer activity.

NOTE
After the initial content transfer, it is recommended to do frequent differential content top-ups to shorten the content freeze period for the final differential content transfer before going live on Cloud Service. If you have used the pre-copy step for the first full extraction, you can skip pre-copy for subsequent top-up extractions (if the top-up migration set size is less than 200 GB). The reason is because it may add time to the entire process.
Also, it is essential that the content structure of existing content is not changed from the time the initial extraction is taken to when the top-up extraction is run. Top-ups cannot be run on content whose structure has been changed since the initial extraction. Ensure that you restrict this during the migration process.
NOTE
Once content paths are migrated to the staging container, those paths or any subpaths within them cannot be removed or excluded from subsequent top-up migrations.
Example: Initial Migration: content/dam/weRetail,
Next Top-up Exclusion Attempt: content/dam/weRetail/ab.
In this scenario, excluding content/dam/weRetail/ab is not possible because the data has already been migrated to the staging container.

Once the extraction process is complete, you can transfer delta content, by using the top-up extraction method.

Follow the steps below:

  1. Navigate to the Content Transfer wizard and select the migration set for which you want to perform the top-up extraction. Click Extract to start the top-up extraction.

    image

  2. The Migration Set extraction dialog box displays. Click Extract.

    IMPORTANT
    You should disable the Overwrite staging container during extraction option.
    image