Follow the steps below to extract your migration set from the Content Transfer Tool:
If Amazon S3, Azure Data Store, or File Data Store is used as the type of data store, you can run the optional pre-copy step to significantly speed up the extraction phase. The pre-copy step is most effective for the 1st full extraction and ingestion. To do so you will need to configure an
azcopy.config file before running extraction. Refer to Handling Large Content Repositories for more details.
You should run User Mapping tool before extracting content from source. See Using the User Mapping Tool for more details.
Select a migration set from Content Transfer wizard and click Extract to start extraction.
Make sure that the Extraction key is valid and is not close to its expiration. If it’s close to its expiration date, you can renew the Extraction key by selecting the migration set and clicking on Properties. Click on Renew. This will take you to the Cloud Acceleration Manager where you can click on Copy Extraction Key. Every time you click on Copy Extraction Key, a new Extraction key is generated which is valid for 14 days from the time of creation.
This will bring up the Extraction dialog. Click on Extract to start the extraction phase.
You have the option to overwrite the staging container during the extraction phase. If Overwrite staging container is disabled it can speed up extractions for subsequent migrations where the content paths or include versions settings have not changed. However, if the content paths or include versions settings have changed, then Overwrite staging container should be enabled.
If the User Mapping has not been run on this migration set prior to extracting content from source, you will see a warning displaying that User Mapping step is pending, as shown in the figure above. Click on Map Users to run the User Mapping tool.
The Extraction field now displays the RUNNING status to indicate that the extraction is in-progress.
You can click on View Progress to get a granular view of the on-going extraction.
You can also monitor the Extraction phase progress from Cloud Acceleration Manager by visiting the Content Transfer page.
Once Extraction is completed, review the other columns like Source and Paths for details of the migration set that you populated by clicking on … and then on View details.
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.
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 1st full extraction, you can skip pre-copy for subsequent top-up extractions (if the top-up migration set size is less than 200GB) because it may add time to the entire process.
Additionally, 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. Please ensure you restrict this during the migration process.
Once the extraction process is complete, you can transfer delta content, by using the top-up extraction method.
Follow the steps below:
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.
The Migration Set extraction dialog box displays. Click on Extract.
You should disable the Overwrite staging container during extraction option.
Once you have learned Extracting Content from Source in Content Transfer Tool, you are now ready to learn the Ingestion Process in Content Transfer Tool. See Ingesting Content into Target to learn how to ingest your migration set from the Content Transfer Tool.