Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Query on CRX2OAK migration

Avatar

Level 2

Hi All,

We are upgrading from AEM 6.1 to AEM 6.3. So we are running CRX2AOK command - java  -jar .jar -v -x crx2oak -xargs -- --load-profile segment-no-ds.

Initially when I ran this command I got a error says that the source and destination are same.

After that i moved the segmentstore inside the repository folder and ran the command again. After I ran this command, a new repository -> segmentstore folder (with some  date attached to the folder name) got created along with the old repository. I ran this command in couple of environments. But the secondary repository/segmentstore folder wasn't created in all scenarios.

In what scenarios a new repository folder will gets created? After upgradation to which repository's segmentstore we need to point?

Thanks,

Swapna

1 Accepted Solution

Avatar

Correct answer by
Employee

hey swapnan23315087

Please follow the below steps on 6.1 repository for successful upgrade cycle :

  • Complete the maintenance tasks like workflow purge, audit purge, version purge
  • Disabling custom login modules(if any like LDAP, SSO etc.)
  • Stop the instance if it is running.
  • Rename/Remove the /crx-quickstart/logs folder
  • Remove the /crx-quickstart/app/cq-quickstart-6.1-standalone.jar file.
  • Rename /crx-quickstart/install folder to /install.bk
  • Delete/Rename the old quickstart jar file and replace it with the new 6.3 one.
  • Unpack the new quickstart jar by running: java -Xmx8192m -jar aem-quickstart.jar -unpack
  • Complete the migration by running : java -Xmx48192m -XX:MaxPermSize=2048m -jar aem-quickstart.jar -v -x crx2oak -xargs -- --load-profile segment-fds (or the required profile depending on your repository structure)
  • Monitor the upgrade.log or the terminal for c.a.g.c.e.MigrationRunner: migration COMPLETED
  • Once done, Start the instance by running: java -Xmx8192m -jar aem-quickstart.jar
  • Tail the error.log and upgrade.log
  • Once instance is started, You should see the login screen for AEM 6.3

View solution in original post

1 Reply

Avatar

Correct answer by
Employee

hey swapnan23315087

Please follow the below steps on 6.1 repository for successful upgrade cycle :

  • Complete the maintenance tasks like workflow purge, audit purge, version purge
  • Disabling custom login modules(if any like LDAP, SSO etc.)
  • Stop the instance if it is running.
  • Rename/Remove the /crx-quickstart/logs folder
  • Remove the /crx-quickstart/app/cq-quickstart-6.1-standalone.jar file.
  • Rename /crx-quickstart/install folder to /install.bk
  • Delete/Rename the old quickstart jar file and replace it with the new 6.3 one.
  • Unpack the new quickstart jar by running: java -Xmx8192m -jar aem-quickstart.jar -unpack
  • Complete the migration by running : java -Xmx48192m -XX:MaxPermSize=2048m -jar aem-quickstart.jar -v -x crx2oak -xargs -- --load-profile segment-fds (or the required profile depending on your repository structure)
  • Monitor the upgrade.log or the terminal for c.a.g.c.e.MigrationRunner: migration COMPLETED
  • Once done, Start the instance by running: java -Xmx8192m -jar aem-quickstart.jar
  • Tail the error.log and upgrade.log
  • Once instance is started, You should see the login screen for AEM 6.3