We are re-architecting the data store for our Adobe Experience Manager (AEM) 
platform and have an encountered an issue when attempting to perform sidegrades 
using the oak-upgrade jar. We're currently on AEM 6.5.13 which uses Jackrabbit 
Oak 1.22.11. The current datastore contains content and assets in a segment 
store. In the new architecture, content will remain in the segment store, but 
assets (binaries) will live in an external data store.

We refrained from doing a live migration because the current platform is used 
24/7 by our global marketing team and we wanted to minimize the impact to their 
day-to-day activities. We take a snapshot of the current repository, move it to 
the new server, and run local migrations there. The initial migration worked 
fine despite the indexing taking 81 days, but the main problem is that every 
time we attempt to perform a migration with only deltas, it continues to 
perform a full migration and duplicate the copying of nodes that already exist 
in the new repository. We're using the following commands to migrate the 
content and the assets (the full paths have been redacted for security 
purposes) :

Content
  /../../java/jdk1.8.0_162/bin/java \
  -server \
  -Djava.awt.headless=true \
  -Xmx48G \
  -jar  /../oak-upgrade-1.22.11.jar \
  /../source/author/crx-quickstart/repository \
  /../target/author/crx-quickstart/repository \
  --src-datastore=/../source/crx-quickstart/repository \
  --datastore=/../target/crx-quickstart/repository \
  --include-paths=/foo/bar,/foo1/bar1 \
  --copy-orphaned-versions=false \
  --copy-versions=2019-01-01

Assets
 /../java/jdk1.8.0_162/bin/java \
  -server \
  -Djava.awt.headless=true \
  -Xmx48G \
  -jar /../oak-upgrade-1.22.11.jar \
  /../source/crx-quickstart/repository \
  /../target/crx-quickstart/repository \
 --include-paths=/foo/bar,/foo1/bar1 \
 --copy-binaries \
 --copy-versions=2025-01-01 \
 --copy-orphaned-versions=false

Any idea why it continues to do a full migration instead of a delta migration 
on subsequent sidegrades?

Also is there anyway to bypass the re-indexing on the target system after every 
delta migration?

Thanks in advance.





Reply via email to