Lakshmi Raghava Reddy Mannem created JCRVLT-655:
---------------------------------------------------
Summary: AEM assets created and createdBy issues
Key: JCRVLT-655
URL: https://issues.apache.org/jira/browse/JCRVLT-655
Project: Jackrabbit FileVault
Issue Type: Bug
Reporter: Lakshmi Raghava Reddy Mannem
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 are using vlt rcp and following is the command that we are using
:
./vlt rcp -r \ -u --no-ordering \ -b $batch_size \ -t $throttle \
[http://$source_server_username:$source_server_password@$source_server/crx/server/crx.default/jcr:root/$source_server_path]
[http://$destination_server_username:$destination_server_password@$destination_server/crx/server/crx.default/jcr:root/$destination_server_path]
So here in the destination server created date property is storing the date
and time that asset copied in destination server and created by is storing as
the username that we are passing instead of that is there way to get the
property that's there in source server instead of overwriting , reason for that
is because of which we can see the wrong information on upload report which is
based on created and createdby , is there any alternate approach to overcome
this. Please let me know if you need any other details. The version that we
are using 3.6.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
