Content Sync between 2 or more Publishers

Using Rep agents is the best way to move content as discussed here -- Replication

If your use case is to sync publish servers without author involvement, then there are couple of options available based on your aem version and other requirements:

1) Use packagemanager and do it manually for each content tree.

2) Use grabbit, rysnc, crx2oak, rcp etc.

links-

http://jackrabbit.apache.org/filevault/rcp.html

https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/using-crx2oak.html

https://helpx.adobe.com/experience-manager/kb/how-to-clone-an-AEM-TarMK-instance-AEM.html

http://adamcin.net/net.adamcin.recap/

https://github.com/TWCable/grabbit

I've read that there are ways to use sling distribution for content as well but I don't think that's the principal use case of this feature.

Hi Gaurav,

Thanks for your reply, We are using 6.4 version. I will check the URL you have shared. 

Di Donald,

Thanks, Till now we were trying to achieve the same using Replication, But we are looking for other options as Gaurav mentioned.

Hi,

I have checked the URLs you have shared, I can see these are used for Migration of content.

But our requirement is below

Getting asset as input from user end and will place the  asset in One publisher, That data need to be sync with all other publisher. It will not be an single time process. Whenever user upload, The synchronization need to be done between publishers.

The mentioned utilities would work for assets as well, check - Assets Migration Guide

Couple of things to keep in mind are

- size of content/assets to sync

- if sync is a periodic/trigger based activity vs a one-time activity

- performance overheads of the solution that you pick

- maintenance/cleanup of assets

Is there any specific reason to abandon usual replication from author to publish and enable publish-sync feature? Would the user still upload assets on author or directly on publish server?

Have you checked binaryless replication where you can use a shared datastore to reduce replication/transport overheads?

Assets Offloading Best Practices

Hi,

Yes, Users will upload the files in front end and that will be placed in Any one publisher instance (It will not move to author).

Can you please let me know which way is the best one to proceed further.

1. Do reverse replication and then move the data from author to all publisher (But in this case, the modified data will change in all publisher, when replication take place. We dont want that to happen)

2. Do replications between publishers (Data will affect when the replication from author instance triggered for same path, since the asset will not be available in author)

These are the ways we planned and the blockers we have. That is the reason we are looking for new approach to proceed further with this sync.

Thanks Gaurav for the update