Redundant Database ServerCore
Instantaneous, graceful failover for your Ovation database server. When the primary DB server fails or needs maintenance, workstations and controllers seamlessly connect to a synchronized secondary—with zero reconfiguration required.
Transparent Failover
Workstations and engineering tools automatically or manually redirect to the secondary DB server. No IP changes, no manual reconfiguration, no interruption to operations.
State Synchronization
The secondary database stays synchronized with the primary. Configuration changes, point modifications, and engineering updates are captured and replicated.
Automatic Health Monitoring
Configurable health checks detect primary DB server failures within seconds and trigger automatic failover to the secondary.
How It Works
Primary DB Server
Handles all operations with a configuration management agent that pulls config to a secondary
Network Daemon
Routes DDB/DCOM traffic between controllers, workstations, and DB servers
Failover Triggered
Failover can be automatic (on failure) or manual (for maintenance/testing)
Secondary Active
Traffic seamlessly routes to secondary with no client changes
| Scope | Database server failover and redundancy for single or multiple highways |
|---|---|
| Failover Time | Seconds (configurable health check interval) |
| Compatibility | Ovation 3.8 (4.0 available) |
