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

How to set up set up master-slave author set up

surendarm613658
Level 3
Level 3

Hi - In my organization, we are planning to set up AEM6.5. AEM 6.5 is already installed on servers A and B and application is running on both the VM's. Currently live traffic is not yet established.

 

I need to know how to set up author in a Master-slave mode.

 

1) In general only A author will be running all time and in case of any author corruption, we need the standby "B author" to be able to handle live request immediately without any manual intervention.

2) Also need to know how to set up A and B in sync mode..i.e..imagine i do a change in A server and same change should get auto reflected in B servers as well..

 

I have tried reviewing many articles over forum but nothing really answered it, please clarify!!!

1 Accepted Solution
aemmarc
Correct answer by
Employee
Employee

we need the standby "B author" to be able to handle live request immediately without any manual intervention.

 

It doesn't work like this. The standby isn't meant as an immediate fail-over per-se. The purpose of the standby instances is to guarantee a live data copy of the master repository and ensure a quick switch without data loss in case the master is unavailable for any reason. It's not instant and it 100% requires manual intervention to get the Standby started as a new Primary. [1]

 

Also -- you'll need to be very familiar with re-building a standby instance from scratch when you apply any major update to the primary Author.  [2]

 

TLDR; Cold-Standby is likely not what you think it is. 

 

[1] -- https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/tarmk-cold-standby....

[2] -- https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/tarmk-cold-standby....

View solution in original post

2 Replies
aemmarc
Correct answer by
Employee
Employee

we need the standby "B author" to be able to handle live request immediately without any manual intervention.

 

It doesn't work like this. The standby isn't meant as an immediate fail-over per-se. The purpose of the standby instances is to guarantee a live data copy of the master repository and ensure a quick switch without data loss in case the master is unavailable for any reason. It's not instant and it 100% requires manual intervention to get the Standby started as a new Primary. [1]

 

Also -- you'll need to be very familiar with re-building a standby instance from scratch when you apply any major update to the primary Author.  [2]

 

TLDR; Cold-Standby is likely not what you think it is. 

 

[1] -- https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/tarmk-cold-standby....

[2] -- https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/tarmk-cold-standby....

View solution in original post

surendarm613658
Level 3
Level 3

Thanks for the valuable details, let me implement the details shared and will get back if any issues