Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Delta/incremental content Migration in AEM 6.2 Tags: CQ

Avatar

Level 6

Hi Team,

 Started migrating the AEM5.6.1 to AEM 6.2. First round completed successfully in lower environments before apply these in production I wanted to know how to do the incremental migration in AEM6.2. 

Here is the situation:

In our case migration taking 5 to 6 complete days. So in the new system, we are losing all these 6 days data. How Can do the delta migration. 

It's very urgent, Any suggestion or approaches that can help me to come out from this situation.

 

Thanks

9 Replies

Avatar

Administrator

I have asked the internal expert to share some thoughts on this.

~kautuk

Avatar

Employee

Hi,

please review the following document[0], it explains the process for a an incremental upgrade:

Incremental migration

If an existing repository is passed as the destination, then only a diff between source and destination will be migrated. It allows to migrate the content in a few iterations. For instance, following case is possible:

  1. migrate a large repository a week before go-live
  2. run the migration again every night (only the recent changes are copied)
  3. run the migration one final time before go-live

I'm not sure why the AEM docs[1] don't reference this.

Regards,

Opkar

[0] http://jackrabbit.apache.org/oak/docs/migration.html

[1]https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

Avatar

Level 6

Hi Opkar/kautuk,

Thanks for the update. I am following exactly the same links. In the documents mentioned these three steps for the incremental migration.  

  1. migrate a large repository a week before go-live
  2. run the migration again every night (only the recent changes are copied)
  3. run the migration one final time before go-live 

 we are planning to do same but there are not many details about the 2nd step. 

How can I exactly run the migration every night?  By using which command that helps me to start working on. 

Thanks in Advance !!!

Avatar

Employee

how did you perform your upgrade? inplace?

Avatar

Level 6

HI Opkar,

I followed these steps for the upgrade

 Steps :

1.    Stop the aem5.6.1 instance. (This box is image of the production).

2.   Place the aem6.2 jar placed next to the aem5.6 crx-quickstart folder.

3.  java -jar aem-quickstart-6.2.0.jar -unpack

4.   java -jar aem-quickstart-6.2.0.jar -v -x crx2oak

5.   java -jar aem-quickstart-6.2.0.jar -v -x crx2oak

6.   java -Xmx16G -XX:MaxPermSize=2048M -jar aem-quickstart-6.2.0.jar -v -x crx2oak -xargs -- -o migrate

This migration took almost 6 days for us. 

Now I am trying to migrate the delta content from the production box again. 

Thanks

Avatar

Level 2

How big is your production repository vs lower environments? Also how many CPU's and total memory do you have assigned to lower environment vs production? Keep in mind that the OS also needs some memory for I/O operations. Do you have a physical box assigned to each environment or are they all running in separate VM's on a single physical box?

Avatar

Level 5

dragon2A wrote...

Hi Team,

 Started migrating the AEM5.6.1 to AEM 6.2. First round completed successfully in lower environments before apply these in production I wanted to know how to do the incremental migration in AEM6.2. 

Here is the situation:

In our case migration taking 5 to 6 complete days. So in the new system, we are losing all these 6 days data. How Can do the delta migration. 

It's very urgent, Any suggestion or approaches that can help me to come out from this situation.

 

Thanks

 

Work with business and get this data, how much content they are updating or adding on every day basis ? Are they ready to do the content freeze till the time you complete the migration activities (6-7 days) ? if everyone is okay with content freeze than you will not loose any data otherwise other options also can be considered.

like - whoever is updating the content in author, make the note of the pages or assets, once migration is completed, create the package of those assets and deploy in the new environment.

Avatar

Level 6

Hi Sandeep,

Content freezing is not possible in our situation.  

We are thinking of that one as well but the problem with the packaging not able to carry the versions. 

We need to carry the content along with the versions. Need other solution to carry that data like merging or copy over the delta content.

 

Thanks

Avatar

Level 10

Are you saying that the documentation provided here: 

https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

does not provide enough information to implement this successfully?