Images are broken when assets are moved from one instance to another instance using cURL command | Community
Skip to main content
sarath3
sarath3
Level 2
March 13, 2018

Images are broken when assets are moved from one instance to another instance using cURL command

  • March 13, 2018
  • 6 replies
  • 5047 views

Any idea why these images are broken when assets are moved from one instance to another instance using the following cURL command:

vlt rcp  -b 100 -n -r -u http://admin:admin@myserver1:4502/crx/-/jcr:root/content/dam/company/categories http://admin:admin@myserver2:4502/crx/-/jcr:root/content/dam/comapny/categories

seeing the following error.

Error while adding node /content/dam/best-western/categories/rep:policy (ignored): javax.jcr.PathNotFoundException: rep:policy. not able to reproduce this issue with when we upload assets through package manager images are working fine.

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

    6 replies

    smacdonald2008
    smacdonald2008
    Level 10
    March 13, 2018

    Because moving Assets from 1 instance to another is bad practice when you using CURL. Its best practice to use Packages and them move them using Package Manager.

      M
      maryw24753203
      Level 2
      May 21, 2018

      I have a similar issue. trying to copy images across environments using vlt rcp command.

      as per the vault logs there are no issues. but the images are broken.

      what is the recommended way to export dam images across environments. using package manager takes lot of time to build these packages (10k+ images to be moved to production)

        joerghoh
        Adobe Employee
        joerghohAdobe Employee
        Adobe Employee
        March 13, 2018

        rep:policy nodes cannot be created via the regular node API, but one needs to use a special API. Don't know if vlt can handle that. On the other hand, can you set a filter not to copy the rep:policy nodes?

          akhoury
          Adobe Employee
          akhouryAdobe Employee
          Adobe Employee
          May 22, 2018

          Try installing a newer version of the vlt rcp bundle to the source and destination instance and try again.  See here for the newest bunde:

          Central Repository: org/apache/jackrabbit/vault/org.apache.jackrabbit.vault.rcp

            J
            jwfife
            Level 2
            July 25, 2018

            I'm facing the same issue, using vlt rcp doesn't seem to copy DAM assets correctly.  The copied images appear to be broken on the destination machine.  Did you found a solution to this that works with vlt rcp?

              sarath3
              sarath3Author
              Level 2
              September 28, 2018

              I  have used packages to move the DAM Assets

                raj_mandalapu
                raj_mandalapu
                Level 7
                September 28, 2018

                Using packages you can mover assets but it will include thumbnails, which makes the package size grow to GB's. I think you can use WinSCP to move content from one system to another and later the DAM workflows will fire and generate thumbnails.

                  A
                  Adobe Employee
                  aneetaroraAdobe Employee
                  Adobe Employee
                  September 28, 2018

                  sarath3​

                  The usage of packages as a solution is not an ideal long-term solution. You can review the "Migrating between AEM instance" section in Assets Migration Guide for best practices. It's a fairly useful document for anyone looking to migrate assets between AEM instances.

                  The reason you're likely facing this issue is because of a bug in vlt tool. The issue is noted in

                  https://issues.apache.org/jira/browse/JCRVLT-186 where the copied binaries are corrupt. The fixed vlt version can be downloaded from https://artifactory.corp.adobe.com/artifactory/maven-aem-release-local/org/apache/jackrabbit/vault/vault-cli/3.1.41-R1801812/vault-cli-3.1.41-R1801812-bin.zip or you can download higher versions as well.

                  Please check if approaching the solution using the vlt version above resolves your issue as well. I've tested it in a couple of scenarios and it has worked well for me.

                  Thanks,

                  Aneet Arora

                    Terms & ConditionsAccessibility statement

                    Loading footer...