Glossary · Availability
Minimize downtime. Maintain operations.
High Availability keeps critical systems operational when local infrastructure fails. With Quorum, HA is not complex clustering or continuously duplicated production infrastructure — it is snapshot-based instant activation designed to bring protected workloads back online in minutes.
Recovery time becomes restart time.
01 The Definition
What is High Availability?
High Availability is an infrastructure strategy designed to minimize downtime during localized failure — keeping organizations operational when individual systems, applications, or infrastructure components stop working.
High Availability keeps systems running when something breaks.
HA is focused on keeping operations moving while the primary site is still accessible. It is most often used to protect against server hardware failure, operating system corruption, application crashes, localized infrastructure disruption, storage or component failure, and planned maintenance windows.
02 Why It Matters
Downtime is not just an IT problem
When systems go offline, the business feels it immediately.
- Users lose access
- Transactions stop
- Customers wait
- Employees work around broken systems
- IT teams shift into emergency mode
The goal is not simply to recover data. The goal is to keep the business functioning.
03 The Old Way
Traditional HA can be complex
Traditional High Availability models often rely on:
- Hardware clustering
- Synchronous storage replication
- Continuously running duplicate infrastructure
- Complex failover configurations
- Specialized network design
- Heavy administrative overhead
These architectures can be powerful, but also expensive, rigid, and difficult to manage. The issue is rarely whether HA is valuable — it is whether traditional HA is worth the complexity.
04 The Quorum Approach
Activation, not duplication
Instead of requiring continuously duplicated production infrastructure, onQ maintains consistent, bootable snapshots of protected systems. When a failure occurs, a protected snapshot is activated on the local recovery platform.
No restore-first workflow. No manual rebuild. No waiting for data movement.
Boot first. Restore whenever.
How Quorum HA works
onQ creates frequent point-in-time snapshots of protected systems, stored locally on the recovery platform and maintained as ready-to-activate recovery points. During a local outage, a snapshot is selected, a virtual clone activates on the onQ system, applications restart, users reconnect, and operations resume — practical for physical servers, virtual machines, and mixed environments alike.
05 The Scope
What HA protects against
High Availability is ideal for localized failure scenarios.
- Server failure
- Application failure
- Operating system corruption
- Storage issues
- Localized power or hardware problems
- Virtual machine failure
- Production host failure
- Maintenance-related downtime
HA is not primarily designed for total site loss. That is where Disaster Recovery comes in.
06 The Distinction
High Availability vs Disaster Recovery
Related, but they solve different problems.
| High Availability | Disaster Recovery |
|---|---|
| Protects against localized failure | Protects against site-level failure |
| Operates within the same site | Operates across locations |
| Focuses on minimizing downtime | Focuses on business survival |
| Uses local recovery infrastructure | Uses remote or cloud recovery infrastructure |
| One protected recovery location | Two protected recovery locations |
Both use the same principle — activate protected systems quickly from consistent snapshots. The difference is location and redundancy.
07 The Layered Model
HA is the foundation for DR
High Availability is often the first layer of resilience — the local protected copy that allows rapid activation during everyday infrastructure failure. DR extends that protection to a second location; DRaaS extends it into Quorum Cloud.
Local resilience
Rapid activation from a local protected copy during everyday infrastructure failure.
Remote resilience
Site-level protection using customer-managed infrastructure at a second location.
One copy restores locally. Two copies ensure survival.
08 Structured Recovery
Policy-based infrastructure activation
HA is not limited to individual servers. Quorum supports policy-based recovery, allowing infrastructure to activate in a structured way.
- Multi-server recovery groups
- Application-tier sequencing
- Domain controller alignment
- Database-first boot policies
- Dependent system coordination
- Grouped infrastructure recovery
Real applications rarely run on one server — a line-of-business platform may depend on authentication, DNS, databases, file services, and application servers. Quorum helps recovery happen in the right order.
Recovery becomes structured, not reactive.
09 Aligning The Metrics
Relationship to RTO and RPO
RTO How fast must systems return?
Because Quorum HA activates systems from local snapshots, recovery time can be reduced significantly compared to restore-first workflows.
Low RTO requires fast activation.
Both must align for effective resilience.
10 Protected By Design
Security within High Availability
Local recovery still needs strong protection. Quorum HA includes controls that protect recovery points from corruption, ransomware, and unauthorized modification.
- Immutable snapshots
- Encryption in transit and at rest
- Logical air gap separation
- Role-based access
- Automated integrity validation
- Recovery testing
Snapshots cannot be modified once written.
Local HA is not just fast — it is protected.
11 The Modern Threat
High Availability and ransomware
Ransomware changes the meaning of availability. A system may still be powered on — but if data is encrypted, operations are down.
Quorum HA supports ransomware recovery by allowing teams to activate from a clean snapshot instead of waiting for a traditional restore. The priority becomes:
For higher-risk events, HA can work alongside Clean Room Recovery to validate systems in isolation before reconnecting them to production.
12 Knowing The Fit
Where HA fits — and where it doesn’t
A strong fit when
- Downtime must be minimized
- Infrastructure remains physically accessible
- Hardware failure is a primary concern
- Applications require rapid local recovery
- Operations cannot wait for full restore
- IT wants simpler failover architecture
- The business needs low RTO for critical systems
Often used for
- Application servers
- Database systems
- Authentication infrastructure
- File servers
- Line-of-business applications
- Virtual machines
- Physical servers
What HA does not replace
HA is local protection. It does not fully protect against complete data center failure, natural disasters, regional outages, building-level power loss, facility loss, or site-wide network failure. The strongest architecture combines all three layers:
13 The Business Case
Economic advantage
Traditional HA can require significant duplicate infrastructure. Quorum reduces that burden by activating workloads from protected snapshots only when needed.
- Less unnecessary hardware duplication
- Reduced cluster management overhead
- No continuous synchronization complexity
- Less manual recovery effort
- Lower downtime exposure
Operational simplicity reduces risk.
14 The Platform
How Quorum supports HA
- Snapshot-based protection
- Instant activation
- Local recovery platform deployment
- Policy-based infrastructure recovery
- Agent and image protection flexibility
- Immutable, encrypted recovery points
- Automated recovery testing
- Clean Room validation
- Optional replication to DR or cloud
Deployable through the onQ Appliance, onQ Flex, or Quorum Cloud as part of a broader recovery strategy.
The deployment model can change. The recovery architecture stays consistent.
15 Put It Into Practice
High Availability checklist
A strong HA strategy should answer:
- Which systems require rapid local recovery?
- What is the RTO for each critical system?
- What is the RPO for each critical system?
- Are dependencies mapped?
- Can systems activate in the correct order?
- Are snapshots frequent enough?
- Are recovery points immutable?
- Is recovery testing automated or regular?
- Does the plan account for ransomware?
- Is DR also required for site-level events?
High Availability works best when it is planned, tested, and aligned to business risk.
Built For The Moment Things Break
High Availability shouldn’t require enterprise clustering complexity.
Quorum delivers HA through snapshot-based instant activation — a practical, reliable way to keep systems operational when local failure occurs, without forcing restore-first delays.
Right onQ. Off Was Never an Option.
Eliminate Downtime from Recovery
Eliminate Downtime from Recovery
Boot systems directly from snapshots and keep operations running without restore delays.