If you want the app to be available, it must support HACMP, and be installed on each side. Usually only one is running and if there is a problem, the other instance is started up. Standby cluster.
BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
it depends on what the customer wants for resillience and what hardware you will be running the services on , for example
if the clinet only has a production environment then you would have one server as the primary server and second as a standby ( i..e standby will be activated if the primary server fails or you moved the production services to the the standby for maintenance work on the primary server)
You can also have the scenario where the client requires production and test/train environments )
Again depending on the nature of the application and the resources it requires to run , you can install the production on the primary server and test/train applications on the standby server, and have it that if the standby server fails the test/train applications don't failover to the primary but if the primary server fails the
production applications fails over to the standby server ( closing the test/train application before starting the production)
You can also have it that production and test/train fails over to the primary and standby servers.
As you can see , it depends on how resilient the client wants their production and or test applications , the cost
( i..e if you want production applications on the primary server and test/train on the standby server , to install test/train on the standby server may require you to purchase more application licenses which costs more whereas if you install production and test/train on the primary server , you don't have this extra cost)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.