1. Where
High Availability
&
Disaster Recovery
meet…

2. When disaster strikes…
We know it comes without a warning.. Be it the fateful
tsunami in Japan or the tornados in the United States!!
Tornadoes per year is
on the rise in US at
an alarmingly high
rate

3. Protecting Business
While there is no way to avert a natural calamity, it is
very much possible to resurrect the business from
where you left.
NMS is no exception as the data it holds is critical to
your business. An in-built disaster recovery mechanism
is therefore important to enable quick recovery.

4. Let’s see how HA is implemented in OpM EE?
Central DB
Probe DB
OpManager Components

5. 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.

6. 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.

7. 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.

8. OpManager’s Reach
Large enterprises can
now look beyond
legacy software like
HP OpenView! Large Enterprises
monitoring
Mid-segment solution

9. OpManager’s Enterprise Readiness
High Availability & • Single-site & multi-site redundancy
Disaster Recovery • Failover & failback
• Manage 50000 interfaces or 5000 devices
Scalability
Remote • Secure communication beyond firewalls/proxys
monitoring • A unified console for multiple sites

10. Need assistance?
Contact: opmanager-support@manageengine.com
www.opmanager.com

11. Thank You!
vidyavasu@manageengine.com