Where High Availability &Disaster Recovery meet…
When disaster strikes…We know it comes without a warning.. Be it the fatefultsunami in Japan or the tornados in the United States!! Tornadoes per year is on the rise in US at an alarmingly high rate
Protecting BusinessWhile there is no way to avert a natural calamity, it isvery much possible to resurrect the business fromwhere you left.NMS is no exception as the data it holds is critical toyour business. An in-built disaster recovery mechanismis therefore important to enable quick recovery.
Let’s see how HA is implemented in OpM EE? Central DB Probe DB OpManager Components
High Availability Deployment The secondary probes have the details of the primary and secondary central servers. On probe failover, the secondary looks up the primary central to send the updates. If it detects the primary central to be down, it automatically starts sending the data to the secondary central server.
Single-site Redundancy Both primary and secondary sharing a single database, preferably in a cluster setup. This model is preferred only if there is a solid cluster setup available.
Multi-site Redundancy Multi-site failover is ideal if you are managing a large enterprise IT that has a nation-wide presence and has datacenters that are located in a ‘calamity-prone’ zone. This approach is preferred only if the cluster redundancy can be set-up across sites.