Can we use vlt rcp to migrate content between two AEM on prem instances using Azure Blob Storage | Community
Skip to main content
M
MayankMo2
July 16, 2024
Solved

Can we use vlt rcp to migrate content between two AEM on prem instances using Azure Blob Storage

  • July 16, 2024
  • 2 replies
  • 797 views

Hi All,

We need to migrate AEM assets between two instances . We are planning to use vlt rcp tool.

The source instance is using Auzre Data Store and target is using different Azure Data store.

 

Can we use vlt rcp in this case or do we need to take different approach. Any suggestions?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by abhishekanand_

Hi @mayankmo2 
No, vlt rcp or the built-in AEM sync tool likely won't work flawlessly for migrating assets when the source and target AEM instances use different data stores. vlt rcp and the AEM sync tool primarily focus on replicating AEM content data itself, not data store configurations. Since the data stores differ, the uploaded data might not be readily usable by the target AEM instance.

My Approach would be to develop scripts using AEM APIs (e.g., Sling API) to handle asset migration and data store interaction.
The script can:

 

  • Retrieve assets from the source Azure Data Store using its specific APIs.
  • Transform assets (if needed) for compatibility with the target data store.
  • Upload assets to the target data store using its APIs.

2 replies

narendrag-aem
narendrag-aem
Level 2
July 17, 2024

Hi @mayankmo2 

 

You could look at using the content sync tool available in ACS AEM Commons as well - https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html

 

Thanks

Narendra

    M
    MayankMo2Author
    July 18, 2024

    Thanks Narendra,

    My doubt is if the source AEM is using Azure data store and target AEM is using different data store, will the vlt or sync tool will work or not for asset migration from source to target? 

     

      abhishekanand_
      Community Advisor
      abhishekanand_Community AdvisorAccepted solution
      Community Advisor
      July 18, 2024

      Hi @mayankmo2 
      No, vlt rcp or the built-in AEM sync tool likely won't work flawlessly for migrating assets when the source and target AEM instances use different data stores. vlt rcp and the AEM sync tool primarily focus on replicating AEM content data itself, not data store configurations. Since the data stores differ, the uploaded data might not be readily usable by the target AEM instance.

      My Approach would be to develop scripts using AEM APIs (e.g., Sling API) to handle asset migration and data store interaction.
      The script can:

       

      • Retrieve assets from the source Azure Data Store using its specific APIs.
      • Transform assets (if needed) for compatibility with the target data store.
      • Upload assets to the target data store using its APIs.
      Abhishek Anand
        Terms & ConditionsAccessibility statement

        Loading footer...