You are here

Whitepaper

Opsview Monitor 5.0 - High Availability & Disaster Recovery Concepts

Opsview Monitor High Availability

Opsview Monitor High-Availability (HA) provides a more resilient master server by allowing failover to a secondary node on the same site in the event of a hardware or software failure. The passive failover server assumes the full identity of the primary master server and including monitoring, alerting, reporting, and data aggregation responsibility. 

The failover / switchover is an automatic, seamless process that ensures Opsview Monitor data collection continuity and is completely transparent to the end user.

Target Architecture: For users that cannot experience any downtime, Opsview Monitor HA provides automatic failover within a single datacenter.

Overview

  • Standby Opsview Monitor Master Server
  • Shared Storage Blocks
  • Heartbeat for Peer Monitoring
  • VIP Swap

Benefits 

  • Automatic Failover

Drawbacks

  • Localized Failover
  • Increased Complexity


Opsview Monitor Disaster Recovery

If a user is looking to handle a situation where the production Opsview Monitor Master Server is lost (e.g. due to machine, network, or site failure), implementing Opsview Monitor Disaster Recovery (DR) may be an appropriate solution. Opsview Monitor DR is distinct from Opsview Monitor High Availability (HA) in that it is not typically intended to provide an immediate or seamless transition from a failed Opsview Monitor System over to its replacement - instead it acts as a ‘warm standby’, where manual intervention is required to move to your DR infrastructure. 

Target Architecture: For users requiring resiliency from datacenter outage using a manual fail over method. 

Overview

  • Standby Opsview Monitor Master Server
  • Replicated Database to Remote Site / DR Infrastructure
  • DNS CNAME Swap

Benefits 

  • Remote Site Failover
  • Low Complexity


Drawbacks

  • Manual Process
  • TTL Dependent Response Time