Hi,
Since we can't cluster 2 author servers using TarMK. I just wanted to know if i can write a cron job to sync the author servers using RSYNC? 1 Server will be always active and whenever there is a change in master i will run a cron job to copy the changed tar files to the other server. Will this work? if yes, which folders should i sync (repository?). if not, why not? :)
Solved! Go to Solution.
Views
Replies
Total Likes
Check out http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys/tarmk-cold-standby.html for Adobe's recommendation on how to achieve a cold stand by highly available authoring TarMK environments (highly available publish environments should follow the TarMK farm model). The model you describe using RSYNC is not a recommended deployment. The cold stand by model requires a restart of the cold stand by instance in order to promote it to primary so it isn't a model that will provide immediate fail over in case of a failure - there will be some noticeable downtime in case of a failover event while the standby is restarted.
Views
Replies
Total Likes
Check out http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys/tarmk-cold-standby.html for Adobe's recommendation on how to achieve a cold stand by highly available authoring TarMK environments (highly available publish environments should follow the TarMK farm model). The model you describe using RSYNC is not a recommended deployment. The cold stand by model requires a restart of the cold stand by instance in order to promote it to primary so it isn't a model that will provide immediate fail over in case of a failure - there will be some noticeable downtime in case of a failover event while the standby is restarted.
Views
Replies
Total Likes
Thanks for the prompt reply. Yes, I just figured out the article published by Adobe.
http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys/tarmk-cold-standby.html
Thanks again for the reply :)
Views
Replies
Total Likes
Hi,
So you want to have a "warm standby" solution? Kicking off a job on every change isn't feasible, as it will change very often (every second?), and you will end up with a few rsync's running in parallel. Instead I would recommend to copy every hour (or every 30 minutes).
kind regards,
Jörg
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies