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

SOLVED

CRX synchronization of two AEM 6.5 instances

Avatar

Level 1

Hi,

 

We would like to synchronize two AEM instances (both running on 6.5, a non-cloud based) with each other. Please suggest best possible practices.

 

This is to align the backup servers with primary servers.

 

Thanks,

Gopal V

1 Accepted Solution

Avatar

Correct answer by
Level 2

You've got a few options.  As another user mentioned, you can use VLT-RCP to sync content from one instance to another.  This, however, comes with the drawback that it only gets you top-level content, and it will not synchronize the version history.  If you're trying to keep an author instance in sync, this is not the best option. 

 

Similarly, you can set up an on-modify replication agent on the author to replicate any modified content to a standby author. This also comes with a similar drawback, and it won't be an exact copy of the primary device either, added to the fact that it's easy for the primary author's replication agents to get backlogged and then your secondary device is out of sync. 

 

Another option is the AEM Cold Standby author product, which has, as its express purpose, keeping up to date an exact copy of the primary device for Authors.  It's been known to be brittle in the past, but it does get the job done. 

 

The other thing that many companies will do, for instances that are running in the cloud, is to simply take a snapshot of the primary device and paste it over onto a cold standby device that you could stand up at a moment's notice.  You don't get real-time updates with this, HOWEVER that can be a blessing as well.  Many of the issues that will take down and author environment (or really create a "mission kill" of an author environment) are unintentional deletions or mass tag corruptions or other such user-initiated items that have nothing whatever to do with a physical outage.  Such issues would be replicated automatically if you have an auto-replication setup, but if you're taking snapshots once every [interval] then you have [interval] time to refer to the backup. 

More on this subject is here:  https://www.opsinventor.com/on-choosing-a-disaster-recovery-strategy-for-adobe-experience-manager/

Hope that helps!

View solution in original post

3 Replies

Avatar

Level 3

Hi @GopalV ,

I believe you are trying to sync all the content as well as users ( in case if you have users in AEM).
So, for content sync VLT-RCP is the best way. There is one similar tools also available named "Grabbit" which also internally use vlt-rcp mechanism. But, it is not supported by Adobe and as well you need to install this to environments. So, maybe in upper environments you might not have access to install this tool.

You can use below command for VLT-RCP to sync asset ( example given considering from local author to pub instance):
./vlt rcp -b 100 -r -u -n http://admin:admin@localhost:4502/crx/-/jcr:root/content/dam/geometrixx http://admin:admin@localhost:4503/crx/-/jcr:root/content/dam/geometrixx-test

Now for user sync you can simply create package of all users and replicate it in all environemts. Otherwise, if you have LDAP then you can easily sync users using LDAP sync process. 
https://experienceleague.adobe.com/docs/experience-manager-64/administering/security/ldap-config.htm...




Avatar

Correct answer by
Level 2

You've got a few options.  As another user mentioned, you can use VLT-RCP to sync content from one instance to another.  This, however, comes with the drawback that it only gets you top-level content, and it will not synchronize the version history.  If you're trying to keep an author instance in sync, this is not the best option. 

 

Similarly, you can set up an on-modify replication agent on the author to replicate any modified content to a standby author. This also comes with a similar drawback, and it won't be an exact copy of the primary device either, added to the fact that it's easy for the primary author's replication agents to get backlogged and then your secondary device is out of sync. 

 

Another option is the AEM Cold Standby author product, which has, as its express purpose, keeping up to date an exact copy of the primary device for Authors.  It's been known to be brittle in the past, but it does get the job done. 

 

The other thing that many companies will do, for instances that are running in the cloud, is to simply take a snapshot of the primary device and paste it over onto a cold standby device that you could stand up at a moment's notice.  You don't get real-time updates with this, HOWEVER that can be a blessing as well.  Many of the issues that will take down and author environment (or really create a "mission kill" of an author environment) are unintentional deletions or mass tag corruptions or other such user-initiated items that have nothing whatever to do with a physical outage.  Such issues would be replicated automatically if you have an auto-replication setup, but if you're taking snapshots once every [interval] then you have [interval] time to refer to the backup. 

More on this subject is here:  https://www.opsinventor.com/on-choosing-a-disaster-recovery-strategy-for-adobe-experience-manager/

Hope that helps!

Avatar

Administrator

@tadreeves Good to have you in the AEM community. AEM community always needs wonderful SMEs like you here.