Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Using Content Transfer Tool - From AEM instance to a Cloud Service instance | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

Using Content Transfer Tool - From AEM instance to a Cloud Service instance by Adobe Docs

Abstract

Important Considerations for Using Content Transfer Tool

Content Transfer Tool now helps you migrate content from a source #AEM instance to a Cloud Service instance

Follow the section below to understand the important considerations while running the Content Transfer tool:
1.The minimum system requirement for Content Transfer Tool is AEM 6.3 + and JAVA 8. If you are on a lower AEM version, you will need to upgrade your content repository to AEM 6.5 to use the Content Transfer Tool.
2. If you are using a Sandbox Environment , ensure that your environment is upgraded to May 29'2020 Release or later. If you are using a Production Environment , it is automatically updated.
3. To use the Content Transfer Tool, you will need to be an admin user on your source instance and belong to the administration group in the Cloud Service instance you are transferring content to. Unprivileged users will not be able to retrieve the access token to use the Content Transfer Tool.
4. During the extraction phase, the Content Transfer Tool is executed on an active AEM source instance.
5. The Ingestion Phase for the author will scale down the whole author deployment. This means that the author AEM will be unavailable during the whole ingestion process.

Read Full Blog

Using Content Transfer Tool - From AEM instance to a Cloud Service instance

Q&A

Please use this thread to ask the related questions.



Kautuk Sahni
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Level 2

hello @kautuk_sahni ,

Would you be able to share some statistics around the usage of content transfer tool? interested in assets migration from non-cloud to cloud(6.4 to cloud)

 

What is a comfortable set size?

How much time did it take for extraction phase on source Author? 

how much time did it take for ingestion phase for that set on target ccloud author?

 

Understand this will depend on instance capacity but still looking for benchmark figures.

This will help plan better. Thanks in advance. 

Avatar

Employee

Hello @asn_india,

 

> Would you be able to share some statistics around the usage of content transfer tool? interested in assets migration from non-cloud to cloud(6.4 to cloud)

Adobe has introduced a new tool called the Cloud Acceleration Manager which will be able to help answer these questions, in addition to helping with other aspects of the transition journey starting from planning to going live on Cloud Service. 

 

> What is a comfortable set size?

This depends on the configuration of AEM's data store: if using a File Data Store, the current limit is 10 TB (Prerequisites for Content Transfer Tool doc link). If using an Amazon S3 or Azure Blob Storage data store, we can transfer binary data much faster in a "pre-copy" step, and this limit does not apply. The CTT documentation covers this approach in Handling Large Content Repositories.

 

> How much time did it take for extraction phase on source Author? 

The Cloud Acceleration Manager provides a "Content Transfer Calculator" which will provide an estimate on what you can expect for a time range, with or without a binary "pre-copy" (as described above, for Amazon S3 or Azure Blob Storage data stores): 

 

Screen Shot 2021-08-04 at 10.39.57 AM.png

 

> how much time did it take for ingestion phase for that set on target ccloud author?

This time will vary based on the size of the segment and data stores on the source AEM instance. Once the initial ingestion is complete, additional "delta" or "top-up" ingestions can be run which will take less time than the initial transfer, relative to the amount of content added. This can help reduce the total "content freeze" time necessary prior to cutting over to the AEMaaCS environment. Please refer to the Using Content Transfer Tool doc for additional details.