The Opsview Monitor distributed architecture combines both
scalability and resilience; however, resilience can, in fact, be effectively enhanced
by ‘doubling’ the Components that comprise your system, as we demonstrate in
the following list.
Master server (active)
Master server (standby)
Database server #1: Opsview and runtime,
replica of data warehouse
Database server #2: Opsview Data
Warehouse, replica of Opsview and runtime
Slave cluster #1;
Slave cluster #2;
Slave cluster #3;
Slave cluster #4.
To achieve an effective doubling of your system, in turn,
enhancing resilience, we provide below, several considerations, which may help
you optimize your system.
The population of the Opsview Data Warehouse (ODW) can be
disabled for short periods of time. Likewise, reporting against the ODW can be
disabled to reduce the overall load;
When assessing a slave cluster, you
should allow the possibility of at least one node failure. If a slave cluster
is nearing capacity, then the failure of one node may cause other nodes to
It is not possible to run two Opsview Monitor master
servers simultaneously, that is, active and active servers.