Now Available

Raising the Bar on Data Availability and Disaster Recovery

with VergeOS 26.1

Improve Data Availability

4x Faster Disk Repair
N+2 Redundancy
ioGuardian for N+X Redundancy

Right-Sized DR

2x Faster Replication
Per-Resource Replication
Tag-Based Snapshots

Two Problems, One Platform

Enterprise data protection has two distinct challenges. First, keeping data available when hardware fails. Second, aligning disaster recovery spend with actual business requirements. Most infrastructure platforms address one or the other. VergeOS 26.1 solves both natively.

Legacy infrastructure versus VergeOS integrated data protection

Slow Repair Extends Risk

When a drive fails, every hour spent in a degraded state is an hour where a second failure could cause data loss. Slow disk repair turns a survivable event into a high-risk window.

Redundancy Gaps

Standard N+1 redundancy protects against a single failure. Organizations that need protection from multiple simultaneous failures have historically required separate storage arrays or bolt-on solutions.

Bandwidth Waste

When every VM replicates to a secondary site on the same schedule, the network carries data from test environments and inactive VMs that no one would prioritize in a recovery scenario.

Recovery Triage Under Pressure

All-or-nothing replication forces IT teams to restore entire environments during a crisis, then sort through the results. Planning should replace triage.

Strengthen Data Availability

VergeOS 26.1 delivers performance and redundancy improvements that change the risk profile of your infrastructure. Faster repair, native N+2 redundancy, and ioGuardian keep data available without adding hardware or bolt-on storage layers.

RF2 and RF3 redundancy with ioGuardian data availability

4x Faster Disk Repair

Reduces the window of degraded-state exposure from hours to minutes. An N+1 configuration that repairs in one hour offers fundamentally different protection than one that takes four.

N+2 Redundancy (RF3)

Native implementation with ioGuardian for organizations that need maximum data availability. Sustains two simultaneous drive failures or a combined drive and node failure.

ioGuardian

Extends data protection beyond standard redundancy levels. RF2 with ioGuardian protects through multiple drive and even node failures, meeting the availability requirements most organizations need without the overhead of RF3.

Faster Controller Recovery

Faster controller walk times after reboot, improved cross-directory file threading, and better storage cache utilization reduce recovery time and improve effective availability across the platform.

Right-Size Disaster Recovery

VergeOS 26.1 introduces per-resource replication, allowing administrators to replicate individual VMs and resources instead of entire environments or tenants. Tags drive protection policies. A VM tagged "production-critical" replicates on a five-minute interval. A VM tagged "dev-test" gets a daily snapshot. A VM tagged "archive" gets excluded entirely.

Comparing VM-centric, data center wide, and VergeOS VDC replication

Tag-Based Policy Control

Assign protection tiers using tags. Change a tag from "dev-test" to "production-critical" and the platform automatically adjusts replication schedule, snapshot inclusion, and recovery priority.

Bandwidth Reclaimed

Stop replicating Tier 3 and Tier 4 workloads. Redirect that bandwidth to tighter RPOs on mission-critical systems or reduce your circuit costs.

DR Storage Right-Sized

When only Tier 1 and Tier 2 workloads replicate, storage consumption at the DR site drops proportionally. Pay for what you need to protect.

No Third-Party Tools

Data protection is a native service in VergeOS, integrated alongside virtualization, storage, and networking under a single management plane. No separate backup console or replication engine.

Workload Classification Framework

Right-sized disaster recovery starts with classifying workloads by business value. Most organizations can categorize their VMs into four tiers. The results are often surprising: 40 to 60 percent of replicated VMs fall into Tier 3 or Tier 4.

Four tiers of workload recovery classification

Tier	Workload Type	Protection Level	Typical VM %
Tier 1: Mission-Critical	ERP, transaction databases, customer-facing apps	Per-resource replication, 5-minute RPOs	10–20%
Tier 2: Business-Important	Email, collaboration, reporting databases	Hourly replication, tag-based snapshots	30–40%
Tier 3: Standard Operations	Dev environments, staging, test labs	Daily/weekly snapshots, no replication	30–40%
Tier 4: Minimal/None	Temporary VMs, POC, decommission candidates	No replication, minimal snapshots	10–20%

See Both in Action

Join the live webinar to see how VergeOS 26.1 strengthens data availability and right-sizes disaster recovery in a single platform.

Tag-Based Partial Snapshots and Faster Replication

Traditional snapshots capture entire environments. VergeOS 26.1 introduces partial snapshots that include or exclude specific resources based on tags, with per-resource quiescing that matches each application's consistency requirements. Improved replication performance extracts more value from existing bandwidth.

Tag-based partial snapshots with per-resource quiescing

Scoped Snapshots

Create a snapshot that captures only VMs tagged "finance-critical" or NAS services tagged "compliance-archive." Leave everything else out.

Per-Resource Quiescing

Databases get application-level quiescing. File servers get filesystem-level quiescing. Stateless web servers get none. Tags control the behavior per resource.

Faster Site Sync

Improved replication performance and bandwidth utilization mean tighter RPOs on the same circuit. Achieve 5-minute RPOs on Tier 1 workloads where you previously hit 15 minutes.

Global Inline Deduplication

Eliminates redundant data blocks before they cross the site-to-site link, reducing both the bandwidth required for any given RPO and the storage capacity at the DR site.

Compliance-Ready

Create snapshot scopes that map directly to regulatory requirements. A "hipaa-ePHI" scope captures only regulated workloads on a schedule that matches HIPAA recovery objectives.

Full Sync Support

Partial snapshots participate in the same replication and recovery workflows as full environment snapshots. No separate tool, no additional licensing.

▸ Frequently Asked Questions

What is per-resource replication?
Per-resource replication allows administrators to replicate individual VMs and resources instead of entire environments. Tags drive protection policies, so a VM tagged "production-critical" can replicate on a five-minute interval while a VM tagged "dev-test" gets a daily snapshot and a VM tagged "archive" gets excluded entirely.

How does 4x faster disk repair improve data availability?
When a drive fails, the cluster enters a degraded state where a second failure could cause data loss. Reducing repair time from hours to minutes shrinks that risk window dramatically. An N+1 configuration that repairs in one hour offers fundamentally different protection than one that takes four.

What is the difference between RF2, RF3, and ioGuardian?
RF2 provides N+1 redundancy, protecting against a single drive failure. RF3 provides N+2 redundancy, sustaining two simultaneous drive failures or a combined drive and node failure. ioGuardian extends protection beyond standard redundancy levels by feeding missing data blocks from a secondary site in real time, giving RF2 configurations protection that approaches or exceeds RF3 without the storage overhead.

How do tag-based partial snapshots work?
Administrators assign tags to VMs and resources, then define snapshot scopes that include or exclude resources based on those tags. Each resource can also receive its own quiescing method. Databases get application-level quiescing, file servers get filesystem-level quiescing, and stateless web servers get none. The snapshot captures only what you specify.

Do I need third-party backup or replication software with VergeOS?
No. Data protection is a native service in VergeOS, integrated alongside virtualization, storage, and networking under a single management plane. Snapshots, replication, and recovery are all built in. There is no separate backup console, replication engine, or additional licensing required.

How does workload classification reduce DR costs?
Most organizations replicate every VM on the same schedule. When you classify workloads into tiers, 40 to 60 percent of VMs typically fall into Tier 3 or Tier 4, meaning they do not need replication at all. Eliminating unnecessary replication reduces bandwidth consumption, DR site storage, and licensing costs while allowing tighter RPOs on the workloads that actually matter.

Does VergeOS 26.1 require new hardware?
No. VergeOS 26.1 runs on your existing servers. The performance improvements, including 4x faster disk repair, 2x faster replication, and global inline deduplication, are software-level optimizations that deliver results on current hardware.

Stronger Availability. Smarter Recovery. One Platform.

Join the live webinar on March 4 at 1:00 PM ET to see how VergeOS 26.1 improves data availability and right-sizes disaster recovery without bolt-on tools or third-party licensing.