You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/09/20 06:24:00 UTC

[jira] [Resolved] (JCRVLT-653) Intermediate saving 500 nodes (4471475 kB)... saving approx 500 nodes... [ERROR] Error during auto save, retrying after refresh: javax.jcr.ItemExistsException: jcr:content[ERROR] rcp: javax.jcr.ItemExistsException: jcr:content

     [ https://issues.apache.org/jira/browse/JCRVLT-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved JCRVLT-653.
------------------------------------
    Resolution: Invalid

> Intermediate saving 500 nodes (4471475 kB)... saving approx 500 nodes... [ERROR] Error during auto save, retrying after refresh: javax.jcr.ItemExistsException: jcr:content[ERROR] rcp: javax.jcr.ItemExistsException: jcr:content
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-653
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-653
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>            Reporter: Lakshmi Raghava Reddy Mannem
>            Priority: Critical
>
> 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 
> but we are getting following exception : 
> Intermediate saving 500 nodes (4471475 kB)... 
> saving approx 500 nodes... 
> [ERROR] Error during auto save, retrying after refresh: javax.jcr.ItemExistsException: jcr:content
> [ERROR] rcp: javax.jcr.ItemExistsException: jcr:content
> though copy success but still wanted to know why are we getting this error, could you please check and let us know the next steps. 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)