Recently in a day care ticket, adobe support team has mentioned that it is suggested to have a separate datastore for standby server.
if we want to implement cold-standby in an existing AEM environment with a file datastore, do we have to copy over the existing datastore to a separate folder and update the configurations accordingly.
Yes you have to take over the datastore to the standby server and remove the sling id. In summary, below steps should give you an idea. These include the datastore configs :
Use the below steps to setup cold standby instance and let me know incase of any issues.
Setting up Primary instance
Setting up the Standby instance
Testing if the cold standby setup works
Config files : Shared Files - Acrobat.com
Thanks for your reply, but these steps are for setting up a new environment.
But, in our scenario we already have an environment with a file datastore configured to a different file path and we are trying to create cold-stand by on top a running instance. The setup is as below
Crx quick start location : /k01/app/aem/crx-quickstart
File datastore location: /l01/aem/datastore
Day care has suggested to create a separate datastore for stand-by server. So, my question was that If we are configuring a cold stand-by now, do we have to copy the file datastore from /l01/aem/datastore to /l01/aem/datastore-standby and then start the standby server pointing the new datastore location or just create a new location and start the server?
Id prefer cloning the current primary instance along with datastore to a new location and start as standby instance as if you start a fresh coldstandby instance, the time to sync over everything from primary would be very high.
if cloning, copy everything along with datastore to a new location, find and delete sling.id file and start as standby instance
if new standby instance, just place correct configs to new aem instance and start as standby and wait for sync to complete
This really helps
As per my knowledge for every restart the sling ID gets changed, do you think it is mandatory to delete the sling.id file?
- As per my knowledge for every restart the sling ID gets changed : This is incorrect.
Only if you clone the instance to another location, you need to regenerate the sling.id file. For a new instance, you don't need to do this.
Could you please suggest the location of sling.id file in crx-quickstart directory?
I am also setting up new cold-standby and installing the primary and standby from scratch on two different hosts. Do I need to be worried about sling.id as both are separate instances from scratch by unpacking aem jar.
Please suggest, thanks!
It worked for us.We followed the below doc and used the attached install folder and conf files in the doc.Please change the IP and path according to your environment.