Agile PLM High Availability
We have a two-server Oracle cluster for Agile development.
Server1 - repository host
Server2 - non-repository host
Regarding restarting the applications and keeping them Highly Available my understanding is that
Server2 (the non-repository host) can be started at will or fail and the users will continue to access the application.
If Server1 (repository host) were to fail the entire application grinds to a halt and servers on both hosts must be restarted.
This is somewhat of a drag if you're trying to keep an application up 24/7. As my boss pointed out a few weeks ago: we have spent a lot of money on redundant routers, power, power supplies, disk arrays ... the the only single-point of failure for Agile is it's repository server.
Server1 - repository host
Server2 - non-repository host
Regarding restarting the applications and keeping them Highly Available my understanding is that
Server2 (the non-repository host) can be started at will or fail and the users will continue to access the application.
If Server1 (repository host) were to fail the entire application grinds to a halt and servers on both hosts must be restarted.
This is somewhat of a drag if you're trying to keep an application up 24/7. As my boss pointed out a few weeks ago: we have spent a lot of money on redundant routers, power, power supplies, disk arrays ... the the only single-point of failure for Agile is it's repository server.
0