Any idea why these images are broken when assets are moved from one instance to another instance using the following cURL command:
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.
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?
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)
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:
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.
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/v... 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.