Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Best ways to move Large set of assets between environments

Shashi_Mulugu
Community Advisor
Community Advisor

Hello Team,

 

We have ~10Lac assets in an AEM instance managed by AMS, and need to move/promote them to higher environments.

 

I have below options

 

  • Vlt-RCP
  • Grabbit
  • Package
  • Replication.

What is the best options along with Pros and cons for each approach.

 

Any other options we have?

1 Accepted Solution
markus_bulla_adobe
Correct answer by
Employee
Employee

Hi @Shashi_Mulugu!

Please refer to the following thread (and linked article) for further options to migrate content, specifically assets, between different environments:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/what-are-the-option-for-as...

 

Quoted from that thread:

  • On top of the already mentioned VLT, the VLT RCP Tool can be helpful.
  • repo is an FTP like tool for JCR content.
  • This adapt.to session recording may also be interesting, it refers to the AEM Easy Content Upgrade tool.
  • For smaller content parts (up top a few GB) content transfers may also be done using CRX packages. However, that's usually not the optimal way for large amounts of assets.
  • If your AEM topology is running at Adobe Managed Services (AMS), your CSE can assist as well. AMS has automated ways for content synchronization available.

There is no one-size-fits-all solution. The right methodology and tool has to be selected based on the specific use case.

 

There are some important points to be considered when transferring assets between instances:

  • If you have custom metadata namespaces, make sure that these are transferred as well. Trying to import assets that have metadata with custom namespaces may fail if the namespace is not available on the target instance depending on the methodology used.
  • Are transferring only original assets or does your transfer already include required renditions?
    If renditions are already included, make sure to deactivate the workflow launchers for the DAM Update Asset workflow to avoid costly re-generation of renditions.
  • Are you using Dynamic Media? If yes, there are instance-specific details in the metadata of your assets that point to the Dynamic Media instance connected to the source instance. Make sure to handle that case properly and (re-) synchronize your assets with/to Dynamic Media on the target instance.

 

View solution in original post

3 Replies
Shashi_Mulugu
Community Advisor
Community Advisor
Hey Ravi, my question is between AEM environments such from QA to Stage to Prod
markus_bulla_adobe
Correct answer by
Employee
Employee

Hi @Shashi_Mulugu!

Please refer to the following thread (and linked article) for further options to migrate content, specifically assets, between different environments:

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/what-are-the-option-for-as...

 

Quoted from that thread:

  • On top of the already mentioned VLT, the VLT RCP Tool can be helpful.
  • repo is an FTP like tool for JCR content.
  • This adapt.to session recording may also be interesting, it refers to the AEM Easy Content Upgrade tool.
  • For smaller content parts (up top a few GB) content transfers may also be done using CRX packages. However, that's usually not the optimal way for large amounts of assets.
  • If your AEM topology is running at Adobe Managed Services (AMS), your CSE can assist as well. AMS has automated ways for content synchronization available.

There is no one-size-fits-all solution. The right methodology and tool has to be selected based on the specific use case.

 

There are some important points to be considered when transferring assets between instances:

  • If you have custom metadata namespaces, make sure that these are transferred as well. Trying to import assets that have metadata with custom namespaces may fail if the namespace is not available on the target instance depending on the methodology used.
  • Are transferring only original assets or does your transfer already include required renditions?
    If renditions are already included, make sure to deactivate the workflow launchers for the DAM Update Asset workflow to avoid costly re-generation of renditions.
  • Are you using Dynamic Media? If yes, there are instance-specific details in the metadata of your assets that point to the Dynamic Media instance connected to the source instance. Make sure to handle that case properly and (re-) synchronize your assets with/to Dynamic Media on the target instance.

 

View solution in original post