Note:
The configuration files also need to be modified so that they match the settings used for the primary instance.
1. Go to the location where the standby instance is installed, and stop it.
2. In case you have a load balancer configured with the setup, you can remove the primary from the load balancer's configuration at this point.
3. Backup the crx-quickstart folder from standby installation folder. It can be used as a starting point when setting up a new standby.
4. Restart the instance using the primary runmode:
java -jar quickstart.jar -r primary,crx3,crx3tar
5. Add the new primary to the load balancer.
6. Create and start a new standby instance. For more info, see the procedure above on Creating an AEM TarMK Cold Standby setup.
The configuration files also need to be modified so that they match the settings used for the primary instance.
1. Go to the location where the standby instance is installed, and stop it.
2. In case you have a load balancer configured with the setup, you can remove the primary from the load balancer's configuration at this point.
3. Backup the crx-quickstart folder from standby installation folder. It can be used as a starting point when setting up a new standby.
4. Restart the instance using the primary runmode:
java -jar quickstart.jar -r primary,crx3,crx3tar
5. Add the new primary to the load balancer.
6. Create and start a new standby instance. For more info, see the procedure above on Creating an AEM TarMK Cold Standby setup.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.