Highlighted

we are following below steps for migration from 6.2 to 6.4.

somayajulud5512

09-07-2019

we are following below steps for migration from 6.2 to 6.4.can any body confirm its correct or need to add any steps

1. java -Xmx4096m -jar cq6.4.0-publish-p2000.jar -unpack -r publish,crx3,crx3tar-nofds,nosamplecontent (unpacking to different folder than 6.2 folder)

2. Modify the .start file

3. Copy install folder to the the crx_quickstart folder for s3 configurations

              3.1. Update  org.apache.jackrabbit.oak.plugins.blob.datastore.S3DataStore.config

              3.2. Update  org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config

4. Start the server with /bin/start file and verify it

5. Once started Install aem-service-pkg-6.4.4.zip

6. Shutdown Server

7. Restart the server.

              8.1 Check the logs all should be good.

9. Install the code and verify

10. Shutdown Server

11. run the Migration Job

              java -Dlogback.configurationFile=./logback.xml \

     -Xmx10g \

     -jar crx2oak-1.8.6-all-in-one.jar \

     segment-old:/data/old /data/AEM/new \

              --include-paths=/content/paths \

              --copy-versions=true \

     --copy-orphaned-versions=false \

              --log-level TRACE

12. Reindex all async Oak indexes (java -Xmx4096m -jar oak-run-1.8.2.jar checkpoints /data/repository/segmentstores rm-all)

13. Start the server

14. Move all files inside /etc/tags to /content/cq:tags

              15.1 Delete /etc/tags folder

              15.2 Restart 'com.day.cq.cq-tagging' bundle (http://10.227.232.215:7000/system/console/bundles)

15. Restart the server

16. Start testing.

Replies

Highlighted

JohnBunker

Employee

09-07-2019

The recommendation is to perform an in-place upgrade following the sequence defined at [1]. What's the reason for not running an in-place upgrade?

[1] Upgrading to AEM 6.4

John

Highlighted

hamidk92094312

Employee

09-07-2019

In the older versions of AEM i.e. < 6.3 a "lift & shift" migration could have been practiced by users but starting AEM 6.3 in-place upgrade is the recommended approach as indicated by John. I even believe engineering does not support any other migration/upgrade scenarios. 

Highlighted

Nirmal_Jose

MVP

09-07-2019

As John mentioned, we should strictly follow Performing an In-Place Upgrade

Few corrections on your steps based on the article are

1. Before running upgrade, you need to do pre-upgrade tasks mentioned in Pre-Upgrade Maintenance Tasks 

2. Stop the instance. Unpack 6.4 jar as a sibling to crx-quickstart folder. While unpacking you dont need the runmode.

3. Do the content migration, during that one, you need to use segment-custom-ds profile as yours is an S3 datastore

4. Update the S3 connector and others in install folder as per your oak version

5. Modify and update the start file and start aem with the existing parameters

6. Move the tags and restart the bundle

7. Index update if needed

8. Restart aem instance and then only proceed with the SP installation.

Highlighted

somayajulud5512

10-07-2019

Thanks all for your replies.

The reason we go as steps mentioned in the above are.

1. we dont want to disturb the existing setup

2. datastore is s3,which is shared across all the author & publish instances.

3.  we want to create new s3 bucket which will be used for new setup.

4.we did it in development environment and it worked without any issues.

regarding the content migration mentioned in  your steps:

Do the content migration, during that one, you need to use segment-custom-ds profile as yours is an S3 datastore. is this approach correct

    java -Dlogback.configurationFile=./logback.xml \

     -Xmx10g \

     -jar crx2oak-1.8.6-all-in-one.jar \

     segment-old:/data/old /data/AEM/new \

              --include-paths=/content/paths \

              --copy-versions=true \

     --copy-orphaned-versions=false \

              --log-level TRACE

Highlighted

Nirmal_Jose

MVP

10-07-2019

If you using a different S3 bucket and a different env stack, then what is not stopping from doing Adobe recommended way?