An Instant Recovery Upgrade

By George Crump

Instant recovery earned its place in the data protection stack. Veeam and other backup vendors built it to restart a workload fast when the production platform is unavailable, and it remains the right answer for that failure. Customers running VergeOS asked for a companion capability, one that shrinks recovery point objectives (RPO) and recovery time objectives (RTO) when the failure never leaves the platform. VergeOS’ ioGuardian answers with real-time, inline recovery, an instant recovery upgrade for failures inside the platform.

Register for the VergeIO webinar on real-time and inline data recovery with ioGuardian

The distinction matters because the two techniques answer different questions. Instant recovery asks how fast a workload can come back somewhere else. Inline recovery asks whether the workload has to go down at all. A VergeOS environment running both covers the full range of failures, from a pair of dead drives in one node through a site loss that takes the whole instance offline.

Key Takeaways
  • Instant recovery and inline recovery answer different failures. Veeam Instant Recovery restarts a workload somewhere else. ioGuardian keeps the workload running where it already is.
  • ioGuardian delivers missing data segments to running VMs in real time, holding RTO at zero with an RPO measured in minutes, with no VM restart and no later move back to production.
  • The ioGuardian target runs on repurposed hardware and holds a third copy of data outside the production instance, with global inline deduplication limiting the capacity it consumes.
  • After failed drives are replaced, the ioGuardian server rebuilds only the missing segments, with no volume-level restore and no RAID rebuild.
  • ioGuardian is included in VergeOS. The only added cost is licensing the server it runs on.

Understanding Real-time Recovery with ioGuardian

ioGuardian for VergeOS is data protection built into the VergeOS code base. Rather than moving a copy of the workload to another platform, it repairs the read path in place, keeping data available even when the hardware protections underneath run out of room during multiple drive or node failures. Instant recovery answers that same event by restarting the VM on a backup appliance. ioGuardian answers it by delivering the missing data segments to virtual machines (VMs) inline, so the workload keeps running.

One of ioGuardian’s key benefits is its ability to tighten RPOs and RTOs. It achieves this through VergeOS snapshots, which run as frequently as the customer needs, pairing regular point-in-time protection with inline recovery. The combination delivers real-time recovery of missing data segments, so VMs keep running while the repair happens behind them. These capabilities are included in VergeOS at no additional charge other than licensing the server used for ioGuardian.

Setting Up Real-time Recovery

The setup for ioGuardian involves configuring a dedicated server as the ioGuardian target, which can be an older, repurposed server or storage system capable of running VergeOS. It runs outside the production instance and represents a third copy of data beyond the protections built-in to the production VergeOS instance.

An Instant Recovery Upgrade

Since it is also running VergeOS, it also provides global inline deduplication, so the storage capacity needed for the ioGuardian server is optimized, allowing for reduced data transfer and footprint. Additionally, placing an ioGuardian server on-premises and at a remote location can enhance data recovery efforts by providing access to data blocks from multiple sources if needed.

Key Terms
Instant Recovery
Re-instantiating a virtual machine directly on a backup appliance so it runs in minutes rather than waiting for a full restore to complete. Veeam Instant Recovery is the most widely deployed implementation of the technique.
Inline Recovery
Delivery of missing data segments to a running virtual machine as the reads occur, so the workload continues without a restart and without a separate restore job.
ioGuardian
The VergeOS data protection service that holds a third copy of data on a separate VergeOS instance and repairs the read path inline during multiple drive or node failures.
RPO and RTO
Recovery point objective is the amount of data at risk between protection events. Recovery time objective is how long the workload stays unavailable before users get it back.
Global Inline Deduplication
Deduplication applied across the entire VergeOS instance as data is written, reducing both the data transferred to the ioGuardian target and the capacity that target consumes.

Comparing Instant Recovery to Real-time Recovery

Several rapid recovery technologies have reached the market over the past decade, and instant recovery is the most widely deployed of them. Veeam Instant Recovery re-instantiates a VM on a backup appliance in minutes. That is exactly what you want when the production platform is down, when the hypervisor itself is the problem, or when the workload has to land on hardware different from where it started. Portability is the point of the technique, and no in-platform capability substitutes for it.

An Instant Recovery Upgrade

Recovery on a backup appliance is a deliberate handoff. IT decides which workloads come up, in what order, and on which appliance, then schedules the move back to production. That control carries real value in a site outage or a ransomware event, where judgment about what to restore matters more than raw speed. It answers a different question than riding through two failed drives inside a single production node.

The two approaches also part ways after the hardware is fixed. A backup product restores full volumes to the replaced drives, which is correct behavior for software that sits outside the platform and cannot see its layout. VergeOS sits inside the platform and knows precisely which segments are missing, so it repairs only those.

ioGuardian handles the in-platform case with no VM restart at all. It supplies the missing data segments in real time, holding RTO at zero with an RPO measured in minutes, and the VMs keep running on production hardware the entire time. Nothing has to move back afterward. When the failed drives are replaced, the ioGuardian server rebuilds the data on them automatically, with no volume-level restore and no RAID rebuild.

Conclusion

The right way to read this comparison is as a division of labor. Veeam Instant Recovery is how a VergeOS workload comes back when it has to come back somewhere else. VergeOS snapshots and ioGuardian are how a VergeOS workload stays up when the failure is inside the platform. Running both produces recovery that is instant in the cases that happen most often and portable in the cases where portability is the only option. ioGuardian is included in VergeOS, so the second layer costs nothing beyond the server it runs on.

To learn more, register for our upcoming webinar, “Can Your Hypervisor Do This? Real-Time and Inline Data Recovery” We spotlight VergeOS’s ioGuardian capabilities, challenging the status quo of hypervisor functionality. Learn what it would take and how much it would cost for other hypervisors to deliver similar capabilities. We will also demonstrate live how ioGuardian delivers missing data segments to virtual machines (VMs), maintaining continuous operations even during multiple simultaneous hardware failures.

Frequently Asked Questions
Does ioGuardian replace Veeam?
No. The two cover different failures. Veeam protects the workload independent of the platform, which is what you need for long retention, off-site copies, ransomware-hardened copies, and recovery onto different hardware. ioGuardian covers failures inside the VergeOS instance, keeping VMs running through drive and node losses. Most VergeOS customers run both.
When should a VergeOS customer reach for Veeam Instant Recovery instead of ioGuardian?
Reach for Veeam Instant Recovery when the workload has to come up somewhere other than the production VergeOS instance. That covers a site outage, a ransomware event where the production copy is suspect, and any recovery onto different hardware. ioGuardian operates inside the instance, so it does not address a failure that takes the whole instance offline.
What happens when more drives fail than the built-in protection tolerates?
ioGuardian supplies the missing data segments inline from the third copy it holds. The VMs keep running on production hardware while the segments arrive, so there is no crash, no restart, and no separate restore job to schedule.
What hardware does the ioGuardian server need?
An older, repurposed server or storage system capable of running VergeOS. Because the target runs VergeOS, it applies global inline deduplication to everything it holds, which keeps the capacity requirement well below the raw size of the protected data.
Can the ioGuardian target sit at a remote site?
Yes. Running one ioGuardian server on-premises and another at a remote location lets the production instance pull data blocks from more than one source, which widens the range of failures the environment rides through.
What does ioGuardian cost?
The capability is included in VergeOS at no additional charge. The only cost is licensing VergeOS on the server used as the ioGuardian target, which is typically hardware already owned and otherwise retired.

Further Reading

The Maintenance Line You Can’t Escape

Scott Bartgis stopped paying VMware maintenance and froze Saratoga Casino Holdings at version 7. The license type was never the problem. The renewal curve was. Here is what a VMware perpetual license buys you, what it costs to hold one unsupported in a regulated environment, and the terms that got him back under support.
Read More

Storage Tiering Without the Capacity Tax

Storage tiering was never an array feature. It was a placement decision that lived where the intelligence sat. Lab measurements show a VergeOS tier change acknowledged in 1.3 seconds with the VM still running, and per-node licensing that decides who captures the data reduction: the customer or the vendor's meter.
Read More

A Pure Storage Alternative

A Pure Storage alternative rarely starts as a storage project. Saratoga Casino Holdings inherited mirrored Pure Storage arrays, Cisco UCS blades, and VMware from a partnership that wound down. Scott Bartgis took the decision back, chose his own nodes through CXTEC equal2new, and removed roughly $50,000 a year in array maintenance.
Read More