Hi all,
I like to ask a question about an upgrade from 6.0 to 6.5. In short, is there a tool that can migrate the 6.0 content to 6.5 in a separate server, and expect minimal fix?
I asked the same question before in a more elaborate fashion, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/upgrading-from-aem-6-0-to-.... We had an internal discussion about it and still have some questions.
Our Repository is Apache Jackrabbit Oak 1.0.22 on AEM 6.0 with sp1, sp2 and sp3. We like to upgrade from 6.0 to 6.5. I read through all the pros and cons of the in-place and fresh installation, and still don't know which one will be better.
Our goal is to transfer all the jsp/jstl to HTL, but it's fine to keep the classic. The most important thing is the content migration. If we rewrite it, the templates paths, references, components repo, etc. will change significantly. I am wondering how the migration tool will handle this. If we rewrite a 6.5 project and install it on a new server, is it possible to copy the old content to the new server? Or any other solution is better than this?
Thank you very much!
-kevin t
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @kevingtan,
Please use crx2oak on fresh installation of AEM6.5 to migrate all the content from 6.0 to 6.5, since AEM6.3 onwards new format for Segment Store has been introduced hence content migration is required. Chose right version of crx2oak jar which has been release with every version of AEM.
There would be downtime required for this activity and will take time as per your repo size.
Perform below steps:
1. Copy source and destination repository at the same server location to avoid network issues
2. Have Fresh destination server
3. Identify the location of source crx-quickstart, datastore, destination crx-quickstart, and datastore.
4. Copy crx2oak jar file and keep it at source server/location under /app/crx2oak .
5. Create 2 blank log files crx2oak.log and migration.log under /app/crx2oak folder
6. Download logback.xml and save it at /app/crx2oak (get logback.xml from this Link )
Now you are ready to run the crx2oak command with options of parameters, I am sharing one such example which I used recently
java -Dlogback.configurationFile=logback.xml -Xmx8192m -XX:MaxPermSize=2048M -jar crx2oak-1.10.0-all-in-one.jar --copy-versions=true --copy-orphaned-versions=true --fail-on-error=true /app/tar/crx-quickstart/repository /author_lcoation/crx-quickstart/repository --src-datastore=/datastore_location/datastore/daily_datastore --datastore=/app/datastore/current_datastore --include-paths=/content/dam/project_root_dam,/content/project_content_root,/jcr:system/jcr:versionStorage > /app/crx2oak/crx2oak.log &
You can see other options associated with crx2oak at this url .
Please let me know if you need more information around it.
Regards
Shya
Hi @kevingtan,
Please use crx2oak on fresh installation of AEM6.5 to migrate all the content from 6.0 to 6.5, since AEM6.3 onwards new format for Segment Store has been introduced hence content migration is required. Chose right version of crx2oak jar which has been release with every version of AEM.
There would be downtime required for this activity and will take time as per your repo size.
Perform below steps:
1. Copy source and destination repository at the same server location to avoid network issues
2. Have Fresh destination server
3. Identify the location of source crx-quickstart, datastore, destination crx-quickstart, and datastore.
4. Copy crx2oak jar file and keep it at source server/location under /app/crx2oak .
5. Create 2 blank log files crx2oak.log and migration.log under /app/crx2oak folder
6. Download logback.xml and save it at /app/crx2oak (get logback.xml from this Link )
Now you are ready to run the crx2oak command with options of parameters, I am sharing one such example which I used recently
java -Dlogback.configurationFile=logback.xml -Xmx8192m -XX:MaxPermSize=2048M -jar crx2oak-1.10.0-all-in-one.jar --copy-versions=true --copy-orphaned-versions=true --fail-on-error=true /app/tar/crx-quickstart/repository /author_lcoation/crx-quickstart/repository --src-datastore=/datastore_location/datastore/daily_datastore --datastore=/app/datastore/current_datastore --include-paths=/content/dam/project_root_dam,/content/project_content_root,/jcr:system/jcr:versionStorage > /app/crx2oak/crx2oak.log &
You can see other options associated with crx2oak at this url .
Please let me know if you need more information around it.
Regards
Shya
Views
Replies
Total Likes
Hi @kevingtan!
Please let me point you to my comment in another thread on the topic of AEM upgrades.
You will see that I outlined different phases for the upgrade from a development point of view:
Looking at the upgrade procedure and content migration, there is also an existing thread that I would like to point you to.
Citing from my comment on that thread:
There are different approaches to upgrade from older AEM versions to newer ones.
From my experience the most reliable and clean way is a combination of these two approaches:
The upgrade process includes rewriting/relocation/transformation of certain elements in the content. This step may get lost if you just migrate your content from an old 6.x instance to a new 6.5 environment using a content migration tool, such as crx2oak. Also for upgrades from 6.0, there are breaking changes involved on the persistence level (changes to the format of the JCR repository). So make sure to follow the official upgrade documentation.
Apart from the "pure" instance upgrade/migration, please also consider the following tasks that make sense and/or are necessary for an upgrade:
Please also note: the bigger the upgrade version step, the more work it is. So plan to test the actual migration process, ideally on a production clone to ensure that you are comfortable with it and there are no surprises during the actual migration run.
Please also refer to these documentations:
Hope that helps!
Views
Likes
Replies
Views
Likes
Replies