{"id":67584,"date":"2024-10-07T11:33:45","date_gmt":"2024-10-07T06:03:45","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=67584"},"modified":"2025-06-30T23:24:12","modified_gmt":"2025-06-30T17:54:12","slug":"a-guide-to-adobe-cloud-managers-content-copy-tool","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/a-guide-to-adobe-cloud-managers-content-copy-tool\/","title":{"rendered":"A Guide to Adobe Cloud Manager\u2019s Content Copy Tool"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

Adobe’s Cloud Manager Content Copy tool is an additional approach that aims to simplify the limitations of using CRX Package Manager \/ VLT RCP and handling huge volumes of content\/DAM copy between AEM environments. The content copy tool in Cloud Manager helps AEM users to copy AMS-hosted AEM 6.x content from Production to Staging or from Production to Development environments. Content Copy Tool typically aims to create a replica of the content in the destination environment. This means the copied content, including assets and associated metadata, should be identical to the source environment.<\/p>\n

Pre-requisites<\/strong><\/h3>\n
    \n
  1. Access to the Cloud Manager Console with Deployment Manager role.<\/li>\n
  2. Access to the AEM Author and Publisher instance to validate the AEM content pages\/DAM assets post the sync process is completed.<\/li>\n<\/ol>\n

    What can be synced?<\/strong><\/h3>\n
      \n
    1. \/content\/*<\/li>\n
    2. \/conf\/*<\/li>\n
    3. \/etc\/*<\/li>\n
    4. \/var\/workflow\/models\/*<\/li>\n
    5. \/var\/commerce\/*<\/li>\n<\/ol>\n

      Availability of this tool:<\/strong><\/h3>\n\n\n\n\n\n\n
      \n

      Platform Model’s<\/strong><\/span><\/h4>\n<\/td>\n

      		\n

      Availability of Content Copy Tool\u00a0<\/strong><\/span><\/h4>\n<\/td>\n<\/tr>\n

      \u00a0AEM On-Prem<\/span><\/td>\nNo<\/span><\/td>\n<\/tr>\n
      \u00a0Adobe Managed Service (AMS) Platform<\/span><\/td>\nAuthor to Author<\/span><\/p>\n

      Publisher to Publisher<\/span><\/td>\n<\/tr>\n

      \u00a0AEM as a Cloud Service<\/span><\/td>\nA<\/span>uthor<\/span> to Author ONLY<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Create a Content Set to update content paths:<\/strong><\/p>\n

      Before the content sync operation can be performed, a content set must be specified. Once defined, content sets can be reused to copy content. Follow these steps to create a content set.<\/p>\n

        \n
      1. Log in to Cloud Manager console at my.cloudmanager.adobe.com.<\/li>\n
      2. Select the appropriate Organization and program.<\/li>\n
      3. From the Service<\/strong> Main Menu, Click on Content Sets<\/strong>.<\/li>\n
      4. Near the top-right of the screen, click Add Content Set<\/strong>.\"1\"<\/li>\n
      5. On the Details tab<\/strong> of the wizard, provide a name and description<\/strong> for the content set and click Continue.<\/strong>\"2\"<\/li>\n
      6. On the Content Paths<\/strong> tab of the wizard, specify the paths of the content<\/strong> to be included in the content set.\"3\"<\/li>\n
      7. Enter the path<\/strong> in the Add Include Path<\/strong> field.<\/li>\n
      8. Click Add Path<\/strong> to add the path to the content set.\"4\"<\/li>\n
      9. In order to restrict content set, sub-paths can be excluded.<\/li>\n
      10. In the list of included paths, click the Add exclude sub-paths<\/strong> icon next to the path that needs to be restricted.<\/li>\n
      11. Enter the sub-path to exclude from the selected path.<\/li>\n
      12. Click Exclude<\/strong> Path.<\/li>\n
      13. Again, click Add exclude sub-paths to add additional paths to exclude as necessary. There are no limits to configure the exclude paths.\"5\"<\/li>\n
      14. Modify the specified paths if required.<\/li>\n
      15. Click the X<\/strong> next to the excluded sub-paths to delete them.<\/li>\n
      16. Click on\u00a0three-dot button<\/strong> next to the paths to reveal the Edit<\/strong> and Delete<\/strong> options.\"6\"<\/li>\n
      17. Click Create<\/strong> to create the content set.<\/li>\n<\/ol>\n

        Perform the Content Copy Operation<\/strong><\/h3>\n

        Once a content set has been created, follow the below steps to copy content.<\/p>\n

          \n
        1. From the Service<\/strong> Main Menu of the Cloud Manager console, navigate to the Content Sets<\/strong> page.\"7\"<\/li>\n
        2. Select a content set from the console and select the copy content<\/strong>\u00a0option from three-dot menu.<\/li>\n
        3. In case a warning message is displayed, this would mean pipeline is in progress and wait for the pipeline to complete.<\/li>\n
        4. In the Copy content<\/strong> dialog box, specify the source<\/strong> and destination<\/strong> environments for content copy action.<\/li>\n
        5. The regions of the target environment must be the same as or a subset of the source environment\u2019s regions. Environment Options may not be selectable if the user does not have the appropriate permissions.<\/li>\n
        6. Select the checkbox Do not delete exclude paths<\/strong> from destination to retain exclude paths that are specified in the content set. If the checkbox is unchecked, then exclude paths are deleted in the target environment.\"8\"<\/li>\n
        7. Choose to copy the version history<\/strong> of paths being copied from source to destination environment. Select checkbox Copy Versions<\/strong> if all version histories need to be copied.\"9\"<\/li>\n
        8. Initiate the content copy from Author to Author<\/strong> and Publisher to Publisher<\/strong> as per above images.<\/li>\n
        9. Click Copy<\/strong>.<\/li>\n<\/ol>\n

          The copy process starts. The status of the copy process is reflected in the console for the selected content set.<\/p>\n

          \"10\"<\/p>\n

          The Content Copy tool won’t allow us to initiate another content copy while the copy operation is already in process.<\/p>\n

          Monitor the Content Copy Activity<\/strong><\/h3>\n
            \n
          1. Monitor the status of copy processes in the Copy Content Activity page.<\/li>\n
          2. From the Service<\/strong> Main Menu, navigate to the Copy Content Activity<\/strong> page.<\/li>\n<\/ol>\n
            \"13\"

            13<\/p><\/div>\n

            Different statuses in the Content Copy Tool<\/strong>
            \nOnce copying content starts, the process can have one of the following statuses.<\/p>\n\n\n\n\n\n\n
            \n

            Status<\/strong><\/span><\/h3>\n<\/td>\n

            		\n

            Status Details<\/strong><\/span><\/h3>\n<\/td>\n<\/tr>\n

            \u00a0In-Progress<\/span><\/td>\n\u00a0 Content copy operation is ongoing<\/span><\/td>\n<\/tr>\n
            \u00a0Completed<\/span><\/td>\n\u00a0 Content copy operation<\/span> failed<\/span><\/td>\n<\/tr>\n
            \u00a0Failed<\/span><\/td>\n\u00a0 Content copy operation completed<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Editing a content set<\/strong><\/h3>\n
              \n
            1. Select an existing content set from the console.<\/li>\n
            2. Select Edit from the three dot<\/strong> menu as shown in below image.<\/li>\n
            3. Update the content path in the existing pipeline and then trigger the content copy operation.<\/li>\n<\/ol>\n
              \"12\"

              12<\/p><\/div>\n

              How to Copy DAM assets to Non-Production<\/strong>
              \nPlease make sure to disable the Workflow “DAM Update Asset<\/strong>” from Workflow Launchers in the Target instance.<\/p>\n

                \n
              1. Please follow the same steps mentioned in the above section “Create a Content Set to update the content paths<\/strong>” to create the consent set for the DAM assets pipeline and “Perform the Content Copy Operation” <\/strong>to copy the DAM assets from Production to Non-Production.<\/li>\n
              2. Better to create a separate pipeline for syncing the DAM assets.\"14\"<\/li>\n
              3. Enter the DAM asset path<\/strong> in the Add Include Path field.\"16\"<\/li>\n
              4. Click Create<\/strong>.<\/li>\n
              5. Please note that the DAM asset copy will take more time than the content copy process.<\/li>\n<\/ol>\n

                Major points to be noted<\/strong><\/h3>\n
                  \n
                1. Both topologies have the same Data Store implementations<\/strong>, i.e. both are File Data Store or shared blob store. It is not possible to sync a shared blob store to a file data store or file data store to shared blob store.<\/li>\n
                2. The target environment must have enough disk space to accept the transferred content. If not, then there is a possibility that the process will consume all available disk space.<\/li>\n
                3. Content copy can only be performed within the same tier (i.e. author-author or publish-publish<\/strong>).<\/li>\n
                4. Instances in both topologies have only one data disk. (except for S3\/Azure BlobStore topologies where cache is kept in a separate disk).<\/li>\n
                5. Target topology can never be Production.<\/li>\n
                6. While the content sync is occurring, no other Cloud Manager actions can be run on the topology. This means that if a sync is being run from Production to stage, a CI\/CD pipeline will not be able to be run.<\/li>\n
                7. Content copy can not be performed if there is any active operation running on either the destination or source environment, such as a CI\/CD pipeline.<\/li>\n
                8. Both Topologies should be in same AWS account or Azure subscription.<\/li>\n
                9. Up to 50 paths<\/strong> can be specified per content set. There is no limitation on excluded paths in the filter section.<\/li>\n
                10. The Cloud Content Copy Tool is primarily focused on copying content nodes and associated metadata.<\/li>\n
                11. Cancelling the pipeline and download logs options are not enabled in the AMS version, and it’s available in the AEM as Cloud version.<\/li>\n
                12. If content is edited in the destination environment, the source content overwrites it if the paths match.<\/li>\n
                13. If the paths are different, content from the source is merged with the content in the destination.<\/li>\n<\/ol>\n

                  Benefits of using this tool<\/strong><\/h3>\n
                    \n
                  1. AEM users can utilise this content copy tool to perform content sync from Production to Non-Production.<\/li>\n
                  2. The content sync process will not cause any space issues.<\/li>\n
                  3. Content Copy UI is simple to use.<\/li>\n
                  4. Another copy operation cannot be initiated while the content sync is in progress.<\/li>\n
                  5. Simply update the content or DAM paths using Path Include\/Exclude options, much like in the CRX Package Manager console.<\/li>\n
                  6. Once the environment details have been updated, the content copy operation is instantly executed.<\/li>\n<\/ol>\n

                    Need Improvements<\/strong><\/h3>\n
                      \n
                    1. Syncing one page path from Source to Destination takes around 30 minutes.<\/li>\n
                    2. If the content sync fails, and reason can’t be figured out in the Cloud Manager UI, because of unavailability of logger to triage the issue, then Adobe CSE need to be contacted to get the detailed log details.<\/li>\n
                    3. There is no error message displayed in the UI console, making it impossible to identify the cause of failure.<\/li>\n
                    4. There is no distinct button to initiate or start the content copying process, as the Content Copy will start immediately once the environment configurations are changed.<\/li>\n
                    5. There is no way to terminate or pause the content sync process once it has initiated.<\/li>\n
                    6. User\/Group nodes cannot be synced through this process.<\/li>\n
                    7. Copy of Version History takes more time than the usual duration.<\/li>\n
                    8. Even if incorrect content path is entered in the filter section, the content copy process is shown as completed. Ideally, if the path does not exist in the AEM repository, the copy operation should fail.<\/li>\n
                    9. Scheduling the sync process is not supported in this tool, initiation of content copy pipeline has to be initiated.<\/li>\n
                    10. Once the sync process is complete, there is no way to revert or roll back the contents.<\/li>\n
                    11. Similar to the Cloud Manager Deployment UI progress screen, the Content Copy UI could show the operation’s phases and progress.<\/li>\n<\/ol>\n

                      Reference Link – https:\/\/experienceleague.adobe.com\/en\/docs\/experience-manager-cloud-service\/content\/implementing\/developer-tools\/content-copy<\/p>\n","protected":false},"excerpt":{"rendered":"

                      Introduction Adobe’s Cloud Manager Content Copy tool is an additional approach that aims to simplify the limitations of using CRX Package Manager \/ VLT RCP and handling huge volumes of content\/DAM copy between AEM environments. The content copy tool in Cloud Manager helps AEM users to copy AMS-hosted AEM 6.x content from Production to Staging […]<\/p>\n","protected":false},"author":1545,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":121},"categories":[5868],"tags":[1522,4847,7144,7394,7147,7145,7146,7393],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/67584"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1545"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=67584"}],"version-history":[{"count":8,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/67584\/revisions"}],"predecessor-version":[{"id":72976,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/67584\/revisions\/72976"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=67584"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=67584"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=67584"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}