|
Eliminate "Planned Downtime"
Augur is designed to run non-stop,
dynamically reacting to configuration changes.
Augur eliminates any need for reconfiguration restarts.
So you can change event streams, change rule sets,
add notification users, etc.
Apply the changes when you want
— all without needing to restart anything.
It just works.
Fault Tolerance
Redundant configuration databases include
network/hardware fault tolerance and recovery.
Two databases work together for high-availability.
If one database fails, the other takes over,
without missing a beat.
Hot Standby
A quick change via the Configuration Editor
can recover from a hardware failure affecting
one of your distributed Augur servers. Either
the affected services (gateway and messengers)
can be reassigned to other Augur servers, or a
spare machine anywhere in your network can be appointed to
take over.
Either way, there is no downtime for the rest of your
system, and no licensing hassles to slow you down.
|
Configuration Database
The primary and secondary configuration databases coordinate concurrent
editing sessions and automatically propagate changes
to all Augur servers, keeping the distributed system synchronized
and appearing as one system.
In the event of a catastrophic hardware failure,
or simple isolation due to LAN/WAN failure,
each distributed Augur server continues operation,
and will automatically reconnect to the enterprise
system when available again.
In isolation mode, Augur servers can still be
individually reconfigured,
to seamlessly support local needs during
a WAN outage.
Changes can be optionally merged with the enterprise
network after the outage.
|
Documents
Augur 4: Survivability