[
https://issues.apache.org/jira/browse/JCRVLT-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742804#comment-17742804
]
Konrad Windszus commented on JCRVLT-654:
----------------------------------------
This is no AEM support channel. Please share an issue with just Open Source
Tools (in the best case a non-working test case).
> Aem assets migration issue while using -n with cq last modified
> -----------------------------------------------------------------
>
> Key: JCRVLT-654
> URL: https://issues.apache.org/jira/browse/JCRVLT-654
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Reporter: Lakshmi Raghava Reddy Mannem
> Priority: Major
>
> Hi Team, We are using AEM 6.5.11.0 product version. Currently we are using
> the currently on TarMK persistence tier and uses block storage, mounted to
> the AEM's VM. Now the data is almost 50 TB and VM's that we are using has
> hard limit 50 TB of data storage, so we can not extend the storage further.
> So to mitigate the issue, we want to move the data storage to object storage.
> For this we are going to new VMs so it's going to be new host entries for the
> production system. So once production VM set up with new object storage. We
> need to migrate the data from existing clone vm of production which is on
> premise one to new VM with object storage. Since data is more we thought of
> using vlt rcp. So in actual vm business uses can perform daily activities. So
> once migration done again we have to do the delta sync from actual vm server
> to new VM server. So for that we thought of using vlt rcp with -n . Following
> is the sample command for the same: ./vlt rcp -r -u -n --no-ordering -b 500
> -t 5
> http://admin:admin@sourceserver-hostname:4501/crx/server/crx.default/jcr:root/content/dam/west-elm/delta-migration-test-data/sub-folder
>
> http://admin:admin@destinationserverhostname:4501/crx/server/crx.default/jcr:root/content/dam/west-elm/delta-migration-test-data/sub-folder
> that command is working fine , if the asset is having property called
> jcr:lastModified to jcr:contnet , where as the asset is having property
> cq:LastModified then it's not working. We did some analysis and came to know
> that cq:lastModified appending when we copy assets from one folder to another
> folder. Also as per the code of following URL :
> https://github.com/apache/jackrabbit-filevault/blob/5d23fe03f4e8675a18baed169c2249edac2a9f8b/vault-core/src/main/java/org/apache/jackrabbit/vault/util/RepositoryCopier.java#L541
> Could you please check and confirm is there any alternate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
