Assets import/export | Community
Skip to main content
J
Johann_Lu
November 3, 2022
Solved

Assets import/export

  • November 3, 2022
  • 3 replies
  • 1762 views

I want to import/export assets from prd, but the assets are too large to import or export. Is there any way to import or export assets from prd to uat?(more than 50G)

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 digarg17

Like I said above , this is technically feasible but depends on use case. For example, is the intent to keep content always in sync or content sync periodically.

As I mentioned , Custom Replication is technically feasible but AMS doesn't support/recommend replication from lower to higher env and if you do1 time  bulk replication from prod thousands of assets - it might be an issue ( if an asset is stuck in queue etc) , in addition to putting load on prod author .

3 replies

D
Adobe Employee
digarg17Adobe Employee
Adobe Employee
November 3, 2022

Usually, one could take a clone of prod and recreate a UAT instance .

Else you can explore below options :

CRX2OAK tool : - https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/using-crx2oak.html?lang=en

VLT-RCP http://jackrabbit.apache.org/filevault/rcp.html

Grabbit - not supported by Adobe

Package manager - not an option for large repo.

 

If you want to automate it you will have to write a custom shell script using vltrcp/crx2oak

 

Custom replication agent using Replication API from prod to UAT is a technically feasible option as well but depends on AEM version and where it is hosted and your use case.

    J
    Johann_LuAuthor
    November 3, 2022

    Are there any other detailed tutorials on CRX2OAK tool?

      krati_garg
      Adobe Employee
      krati_gargAdobe Employee
      Adobe Employee
      November 3, 2022

      @johann_lu 

      Package Manager is the recommended way to move Content Or Assets between the environments.
      Package Size do not have a written limitation from Adobe. I have seen customers who have tried to and succeeded in building Packages size as huge as 50GB and more
      Again, it also depends on various factors like Network Latency, depth of Path Filter in Package that can contribute to Timeout while building such packages.

       

        diksha_mishra
        Community Advisor
        diksha_mishraCommunity Advisor
        Community Advisor
        November 3, 2022

        @johann_lu We did setup a new replication agent in Source AEM Instance, setup the Target instance URL, and initiated Tree Replication at folder levels to push the assets. It worked perfectly and better than the other described ways. 

          D
          Adobe Employee
          digarg17Adobe EmployeeAccepted solution
          Adobe Employee
          November 3, 2022

          Like I said above , this is technically feasible but depends on use case. For example, is the intent to keep content always in sync or content sync periodically.

          As I mentioned , Custom Replication is technically feasible but AMS doesn't support/recommend replication from lower to higher env and if you do1 time  bulk replication from prod thousands of assets - it might be an issue ( if an asset is stuck in queue etc) , in addition to putting load on prod author .

            Terms & ConditionsAccessibility statement

            Loading footer...