Hot Standby Appliance

For organizations where an outage is not an option, SevOne provides the best high-availability network performance management solution in the industry. Using the same hardware and software as a primary appliance, a SevOne Hot Standby appliance is configured to maintain its memory cache and disk storage in sync with the primary appliance. While in standby mode, it does not perform any active monitoring itself and therefore it places no additional strain on the network. In the case of primary appliance failure, the Hot Standby takes over the monitoring functions of the failed appliance providing continuity for your network performance management needs. Failover occurs in less than 30 seconds and transparently assumes the primary polling and reporting responsibilities.
 

SevOne's Intelligent Distributed Architecture
SevOne's peer-to-peer distributed architecture utilizes redundant hardware and software to guarantee maximum reliability and speed

The only enterprise-ready Hot Standby appliance in the market today, SevOne makes full and efficient use of the seamless distributed peer-to-peer architecture behind SevOne. Because each appliance on the network can be used standalone or joined with others in a peering environment, both redundancy and linear scalability are assured. In this way, SevOne solutions have the unique ability to scale linearly and to readily span even the world’s largest networks.

 

SevOne: A High Availability Solution
The SevOne Hot Standby solution assumes data collection responsibly from the primary server in real-time. Fallover occurs in 30 seconds or less.

By default, SevOne's Hot Standby solution provides a true one-to-one backup. Because each Hot Standby appliance needs to assume polling functionality, and be able to store all the historical data of the primary it is backing up, storage requirements can range upwards of a terabyte - all of which is included in the appliance. After failover occurs, all historical data is still available for reporting, alerting and forecasting from the secondary appliance - in other words, historical reporting is not impacted by primary appliance failure.