crx2oak - datastore migration

[sreenivasula]

Hello All,

We are using AEM 6.0 and configured our repository to use a FileDataStore(ex: /home/aem-datastore/datastore) and segment store  is under default location( crx-quickstart/repository/segmentstore)

Now we are upgrading from AEM 6.0 to 6.3.  We are using crx2oak tool to migrate repository with below command.

AEM 6 repository path:- /local/data/aem6/author/DEVREPO/repository (We copied both our datastore and segmentstore manually to this path, accessible from AEM 6.3 host machine)

AEM 6.3 repository path:- /local/data/aem63/author/crx-quickstart/repository

java -Xmx10g -jar crx2oak.jar  --src-datastore /local/data/aem6/author/DEVREPO/repository/datastore --datastore /local/data/aem63/author/crx-quickstart/repository/datastore --include-paths=/etc/tags/abc,/content/abc,/content/xyz,/content/def,/content/dam segment-old:/local/data/aem6/author/DEVREPO/repository /local/data/aem63/author/crx-quickstart/repository

Migration is successful, but the size of AEM 6.3 datastore(/local/data/aem63/author/crx-quickstart/repository /datastore) is very small in size (AEM 6.3:- 94 GB AEM 6.0 is 10  GB) than that of AEM 6.0(/local/data/aem6/author/DEVREPO/repository/datastore).

So the question is, when migrating from AEM 6.0 to 6.3, if FileDataStore is configured in AEM 6.0, do we really need to migrate datastore to AEM 6.3 using crx2oak ? or we can directly use AEM 6.0 datastore in AEM 6.3?

If we can’t use directly, please let us know correct options for crx2oak tool to migrate datastore from AEM 6.0 to 6.3

Thanks in Advance

[Kunwar]

crx2Oak side-grade or side-migration is not supported by Adobe. Please be careful if you move ahead with this approach.

crx2oak tool should only be used in 2 scenarios:

1. Migrating content from lower environment to higher environment running the same version of AEM

2. At the the time Go-Live cutover where only the delta content needs to be moved from 6.x to 6.3

If you go ahead with a full side-grade using crx2oak tool, you would run into multiple issues with users, saml,msm etc. as there are multiple upgrade tasks that need to be performed by the upgrade utility in the inplace upgrade.

P.s : We don't recommend running the migration using crx2Oak tool for a full migration cycle from 6.0 to 6.3

[sreenivasula]

Thanks for your quick reply. But we are not using crx2oak tool for full migration, we are only migrating some pages and assets (mentioned in include path). Our main query is on data store migration.

Thanks in advance

[Kunwar]

OK if that's the case, in 6.0 is the datastore external or everything goes inside the segmentstore ?

If it is external, you need to to specify the --src-datastore along with --copy-binaries flag

if it internal, you should just add the --copy-binaries flag

[sreenivasula]

Thanks Kunwar! Our datastore is external, so I used the options suggested, but still I see a huge difference in size of old and new datastore. Any idea what's wrong here? But migration is successful.

Below is exact command used.

java -Xmx10g -jar crx2oak.jar --copy-binaries --src-datastore /local/data/aem6/author/DEVREPO/repository/datastore --datastore /local/data/aem63/author/crx-quickstart/repository/datastore --include-paths=/etc/tags/abc,/content/abc,/content/xyz,/content/def,/content/dam segment-old:/local/data/aem6/author/DEVREPO/repository /local/data/aem63/author/crx-quickstart/repository

Please help

[Kunwar]

Although you can check why the size is different by checking the Disk usage report but I think there's an issue with indexing on your 6.3 instance post migration if AEM 6.3:- 94 GB AEM 6.0 is 10  GB

Check the jmx console and see index stats on the size of indexes. Also, Do a cycle of compaction and Datastore gc to clean all the garbage present currently in the system to get a better estimate on state and size of repository

[sreenivasula]

Thanks Kunwar! The size difference is vice versa, i.e, source datastore is 94 GB and destination datastore is 10gb.

[Kunwar]

OK then it comes to the question, before the inplace upgrade, did you run the version purge, workflow purge, offline compaction and datastore gc ? If there were GBs on indexes( for any reason) they wont be migrated to 6.3