High Availability, Data Protection and Disaster Recovery Built Into VergeOS
Conventional infrastructure buys high availability, snapshots, backup, ransomware recovery and disaster recovery as separate products. VergeOS, the private cloud OS, builds all of them into VergeFS as one layered architecture, included in every license.
Five Protection Products That Never Agree
In a conventional stack, the hypervisor handles failover, the array takes snapshots, backup software keeps copies, a security tool watches for ransomware and a replication product handles DR.
Each one runs on its own schedule, with its own retention and its own upgrade cycle. When something breaks, the team has to work out which copies are clean and which products still agree with each other. Recovery gets fragile exactly when it matters most.
VergeOS builds protection into the write path
- Synchronous replication protects every new block before the write is acknowledged
- ioGuardian keeps VMs running through failures beyond the replication level
- IOclone snapshots recover an instance, a VDC, a VM or a single file
- ioFortify spots encryption inside the storage layer
- ioReplicate moves whole Virtual Data Centers to a DR site
- Every capability ships in the same per-server license
A Server Fails. The VMs Keep Working.
High availability is the default behavior of VergeOS, not a separate controller. When a server fails, VergeOS restarts its virtual machines on other servers in the instance. A predictive placement algorithm picks the best node for each VM, so performance holds through the failed state.
The same redundancy covers planned work. VergeOS upgrades roll one node at a time with zero downtime, from one code base on one cadence.
VMs from a failed node restart across the instance.
Protection Starts the Moment Data Is Written
When a VM writes to VergeFS, VergeOS captures the data in memory first. Global inline deduplication examines it in 64K segments. If the segment already exists, VergeOS updates metadata only, with no storage write and no network traffic.
A new segment is written synchronously to multiple storage nodes before VergeOS acknowledges the write to the VM. Always-on deduplication typically delivers 4:1 or better, with almost no performance impact, and it is the same engine that powers snapshots, replication and ransomware detection.
- RF2. Two copies on separate nodes and drives. Survives one drive or one node failure.
- RF3. Three copies. Survives two drive or two node failures.
- Mixed nodes. Any node that contributes storage, including storage-only nodes, takes part in protection.
Duplicates cost nothing. New data is protected before it is acknowledged.
When Failures Exceed RF2 or RF3, VMs Keep Running
ioGuardian is an independent protection layer: one extra server that holds a complete copy of the instance’s data. It protects the whole VergeOS instance, not individual disks or storage groups.
If failures exceed the replication level, VergeFS pulls missing blocks from the ioGuardian server and feeds them to the requesting VMs in real time. Applications keep running without immediate administrator action. The only cost is some added latency during retrieval.
- The ioGuardian server can be older hardware with HDDs
- Deduplication shrinks the data before it reaches the server
- The capability is built into VergeFS. You license the server, not the feature.
Multi-layer retrieval keeps data flowing through complex failures.
Independent Snapshots, Kept as Long as You Need
Traditional snapshots depend on the snapshot before them, so frequency and retention cost performance. IOclone snapshots are metadata-based and act like independent, standalone copies. Take them as often as every 10 to 15 minutes and keep them for months without a performance penalty.
- Any level. Snapshot and recover the entire instance, a Virtual Data Center or a single VM.
- File-level recovery. Mount a VM snapshot to the production VM as a drive and copy files back. Thousands of files restore almost instantly through metadata remapping.
- Read-only by default. Mark selected snapshots immutable so they cannot change or be deleted before retention expires.
- 3-2-1 ready. Snapshot independence helps meet the 3-2-1 rule of backup.
Frequency and retention without a performance penalty.
Detect in Minutes, Recover by Promotion
The average ransomware dwell time is six days. VergeOS shortens detection to 10 to 15 minutes and replaces restore-from-backup with snapshot promotion.
Contain
Each Virtual Data Center has its own networks, storage volumes and access controls. An attack that enters one VDC stays in that VDC.
Detect
Encrypted blocks are unique, so an attack breaks the deduplication trend. ioFortify alerts within 10 to 15 minutes of an encryption event starting.
Recover
Mount a 15-minute-old snapshot in quarantine, scan it, remove any payload and promote it to primary. No restore, no waiting for capacity, no per-VM rebuild.
Trust the Copy
Snapshots are read-only by default and independent of each other, with an immutable option the attacker cannot alter.
Virtual Data Centers Simplify Disaster Recovery
Traditional DR stitches together data, VMs and network settings from separate products, and the test fails most years. A VergeOS Virtual Data Center packages VMs, networking, IP addressing, storage settings and security policies as one object.
ioReplicate sends VDC snapshots to a second VergeOS site whenever a protected snapshot is created. Deduplication runs across the WAN, so only unique blocks travel. The replica includes every configuration detail, so it runs correctly on different servers, storage and networking at the DR site.
- Three-click recovery of an entire VDC
- DR tests take less than an hour, so customers run them as a routine
- Customers report a 100% DR test success rate with VDCs
The whole environment arrives with its configuration intact.
Four Bad Days, Two Outcomes
The architectural argument stays theoretical until something breaks. Here is how the operations day changes.
| Scenario | Conventional Stack | VergeOS |
|---|---|---|
| Multi-drive failure beyond the protection level | Restore affected VMs from backup, typically 4 to 8 hours stale. Hours of downtime and data loss. | ioGuardian serves missing segments in real time. VMs keep running, RPO in minutes. |
| Ransomware attack | Array, hypervisor and backup each have their own snapshots and rules. The team verifies which copies are clean. | VDC isolation contains it, ioFortify alerts in 10 to 15 minutes and a clean snapshot is promoted. |
| The annual DR test | Coordinated across array replication, hypervisor failover, network changes and the backup catalog. Often fails. | Three-click recovery of an entire VDC, even on different hardware. Run it routinely. |
| Planned upgrade | Five products on five cadences, each regression-tested against the other four. | One code base on one cadence. Rolling node-by-node upgrades with zero downtime. |
VergeOS Protects the Infrastructure. Veeam Protects the Workload.
Veeam Backup & Replication 13.1 supports VergeOS natively through the Universal Hypervisor API. Run both layers. VergeOS handles the fast, local recovery: the 10-minute-old mistake, the multi-drive failure and the site outage. Veeam handles long-term retention, independent immutable copies, application-item recovery and restores onto other platforms.
VergeOS also works with other UHAPI or oVirt-compatible backup software.
Included in Every VergeOS License
VergeOS is licensed per physical server. Every protection capability on this page ships in the same license, with no add-ons and no metered services.
Frequently Asked Questions About VergeOS Availability and Protection
How does VergeOS provide high availability?
High availability is the default behavior of VergeOS. When a server fails, VergeOS restarts its virtual machines on other servers in the instance, and a predictive placement algorithm picks the best node for each VM. Upgrades roll one node at a time with zero downtime.
What is the difference between RF2 and RF3?
Replication Factor 2 keeps two copies of every block on separate nodes and drives and survives one drive or one node failure. Replication Factor 3 keeps three copies and survives two drive or two node failures. In both cases VMs stay online and protection rebuilds in the background.
What happens if failures exceed RF2 or RF3?
ioGuardian takes over. An extra server holds a complete copy of the instance’s data, and VergeFS pulls missing blocks from it and feeds them to running VMs in real time. Applications keep running without immediate administrator action.
Does ioGuardian cost extra?
The ioGuardian capability is built into VergeFS at no additional cost. Customers license the additional server, which can be older hardware with HDDs.
How does global inline deduplication help data protection?
VergeOS examines every write in 64K segments. Duplicate segments update metadata only, which typically delivers 4:1 or better deduplication. The same engine makes snapshots and replication efficient and powers ioFortify ransomware detection.
How are IOclone snapshots different from traditional snapshots?
Traditional snapshots depend on the snapshot before them, so frequency and retention cost performance. IOclone snapshots are metadata-based and act like independent copies, so they run every 10 to 15 minutes and are kept for months without a performance penalty.
Can I recover individual files from a snapshot?
Yes. Mount a VM snapshot to the production VM as an additional drive and copy the files back. Thousands of files restore almost instantly through metadata remapping.
How does VergeOS protect against ransomware?
Virtual Data Center isolation contains an attack. ioFortify watches the deduplication trend and alerts within 10 to 15 minutes of an encryption event. Recovery promotes a clean snapshot to primary instead of restoring from backup, and immutable snapshots cannot be altered.
How do Virtual Data Centers simplify disaster recovery?
A VDC packages VMs, networking, IP addressing, storage settings and security policies as one object. ioReplicate sends it to a second VergeOS site, where it recovers in three clicks and runs correctly on different hardware. Customers report a 100% DR test success rate.
Do I still need backup software with VergeOS?
VergeOS handles fast, local recovery, and backup software handles long-term retention, independent copies and restores onto other platforms. Veeam Backup & Replication 13.1 supports VergeOS natively, and VergeOS works with other UHAPI or oVirt-compatible backup software.
Resilience Without the Product Sprawl
High availability, data protection, ransomware recovery and disaster recovery in one platform, one license and one upgrade path.