Edge disaster recovery means stores, venues and restaurants stay open through a failed drive, a ransomware attack or the loss of the local server. VergeOS 26.2 handles all of them.
Edge disaster recovery becomes urgent when the remote location serves customers directly. Entertainment venues, restaurants, retail stores, and customer service centers all share the same goal. Nobody standing at the counter should hear, “I’m sorry, our system is down,” or “the internet is out.” That sentence frustrates the customer and makes your brand look bad. VergeIO customers like Topgolf and Saratoga Casino run exactly these kinds of locations. In our on-demand webinar, VergeOS 26.2: Finish the VMware Exit, Dave Vincent showed how VergeOS keeps them serving customers through two very different kinds of failure: problems inside the site, and the loss of the site itself.
Key Takeaways
- VergeOS runs a remote site on as few as one server, new in VergeOS 26.2, or on a small two-node HA cluster, with data protection built in so no local IT staff is required.
- Drive failures, deleted files, corruption, and ransomware recover locally from VergeOS snapshots, and ioGuardian pulls missing blocks from the core when failures exceed the protection level.
- Each site runs as a Virtual Data Center that replicates to the core on your schedule, so the core can run the entire site if the local servers go offline.
Edge Disaster Recovery Starts With Running Local
The main reason to keep servers at a remote location is to serve customers and keep operations running when the site is disconnected. If you are at Topgolf having fun, you want the fun to keep going when the internet connection drops. The problem with running local is that you probably can’t afford IT staff at each location. That means the infrastructure must be managed remotely, rely on automation, and provide local data protection and resiliency.
VergeOS meets this demand by running on as few as one server at a remote site, new in our 26.2 release. For local high availability, a small two-node HA cluster does the job. With no IT staff on site, these systems are exposed directly to the people using them, so VergeOS builds data protection and resiliency into the platform to guard against drive failures and accidental data deletion.
Drive Failures
When a drive fails, VergeOS redirects reads and writes to the surviving redundant drives and the site keeps running. If the number of failed drives exceeds your protection level, for example two drives failing, VergeOS uses ioGuardian to transfer the needed blocks from the core data center to the venue or store. The only expense is the latency of moving those blocks across the wire. Customers keep checking out, and IT replaces the drives on its own schedule.
Deleted Files, Corruption and Ransomware
If a user deletes a file or an application suffers corruption, VergeOS snapshots let you restore an individual file by mounting a snapshot as a drive to a virtual machine. Severe corruption or a ransomware attack calls for a bigger response, since ransomware is an infrastructure problem that reaches the VMs, the network and the configuration along with the data. VergeOS system snapshots restore the entire site locally, at local speed, without waiting on WAN bandwidth.
Follow our best practice: put each remote location in its own Virtual Data Center, and keep an attack contained to that site. Ransomware can’t creep up the wire into the core data center or spread to other remote sites.
Edge Disaster Recovery When the Whole Site Goes Down
The second edge disaster recovery situation is the loss of the entire site. Single-server sites are especially vulnerable because there is nothing left to fail over to. The risk is a location that is technically open for business. Customers walk in the door, and the kitchen is open, but without the servers, nothing can be transacted.
VergeOS addresses this by establishing each remote location as a Virtual Data Center (VDC). A VDC encapsulates the entire remote data center into a single object, and VergeOS replicates that object to the core data center on a schedule you set. Each replication captures the site’s complete state, including data, network configuration, VM configurations, and storage settings, all consistent and in sync. The core holds everything it needs to run the remote site. VergeOS abstracts the hardware, so that VDC runs at the core even when the core uses different server, storage, and network hardware than the store.
| Failure | VergeOS Response | Where Recovery Runs |
|---|---|---|
| One drive fails | Reads and writes move to surviving drives | Local |
| Failures exceed protection level | ioGuardian supplies missing blocks from the core | Local, with blocks from the core |
| User deletes a file | Snapshot mounted as a drive to a VM | Local |
| Corruption or ransomware | System snapshot restores the whole site | Local |
| Site servers go offline | Replicated VDC runs the site, BGP redirects traffic | Core |
See the Failover in the On-Demand Webinar
In the webinar, Dave used VergeOS’s built-in BGP routing to show the core copy of a remote location picking up the moment the remote servers went offline. The store keeps serving customers from the core, and IT can fix or replace the local hardware on its own schedule. Watch the on-demand webinar for the full session, or go straight to the Edge Site Recovery Demo. The VergeOS 26.2 datasheet covers single-server sites and the rest of the release. If you want to map this to your own locations, book a technical whiteboard session with our team.
Key Terms
Frequently Asked Questions
Can VergeOS run a remote site on a single server?
What happens if two drives fail in a single-server site?
Does ransomware at one store reach the core data center?
What does the core need to run a failed remote site?
Next Steps
The full webinar, the edge recovery demo and the datasheet are one click away.
Gartner’s planning data projects that 55 percent of enterprises will be in proof-of-concept evaluations of VMware alternatives by 2028. Industry reporting on VMware price increases under Broadcom shows a range from 50 percent to over 1,000 percent for affected customers. CloudBolt’s 2024 survey found 99 percent of IT decision-makers reporting concern about the acquisition’s impact. These three numbers explain why the migration question is no longer optional for most VMware shops. They do not explain why the backup tier needs to be redesigned alongside it.
Single-product VMware exit data protection fails one of two tests. Infrastructure-only protection lives inside the virtualization platform. It handles hardware failures and operational continuity well, but offers no compliance retention, no air-gapped immutability, and limited defense against ransomware targeting the production cluster itself. Backup-only protection can take minutes to hours to recover after a hardware event and depends entirely on backup scheduling for meaningful protection.
The numbers point to a single architectural answer. A backup that lives in the same trust domain as production has been compromised by definition once an attacker reaches the production system. Immutability has to exist at both layers. ioClone snapshots inside VergeOS are read-only by default and can be set to immutable by checking a box. As a result, they cannot be modified by an attacker who reaches the production cluster. Storware adds immutable storage targets, such as S3 Object Lock and Data Domain Retention Lock, outside the cluster trust domain. Recovery from in-cluster snapshots is near-instant. Recovery from the Storware tier is slower but provides the long-term retention horizon for compliance and forensic analysis.
