VergeFS: The vSAN Alternative Built Into VergeOS
VergeFS is the storage layer inside VergeOS, the private cloud OS. It pools the drives in your servers, accepts capacity from the Fibre Channel arrays you already own, and deduplicates every write inline, all in the same code base as the hypervisor and the network.
Legacy vSAN runs storage as a guest of the hypervisor
Most hyperconverged platforms deliver storage as a separate software package. A controller VM, or a storage module bolted onto the kernel, sits on every server and competes with production workloads for CPU and memory. The hypervisor has no view into what the storage layer is doing, so every I/O takes the long way around.
- Storage software consumes cores and RAM on every node
- Existing SAN arrays get retired instead of reused
- Deduplication stops at the storage boundary, so the network still moves duplicate data
VergeFS is part of the operating system
VergeFS ships inside VergeOS. The hypervisor, the network and the storage layer share one code base and one data model, so the hypervisor knows where every block lives and every server reads and writes through the shortest path. There is no storage VM to size, patch or license.
- Storage, compute and networking install as one package
- Fibre Channel arrays and storage-only nodes join the same pool
- Deduplication runs inline and globally, so redundant segments never cross the network
A Hypervisor with Storage Built In
VergeFS is directly integrated into VergeOS. It is a native service of the operating system, so the hypervisor is aware of every VergeFS function, from block placement to snapshots. That awareness lowers overhead on every server and shortens the I/O path for every VM.
The result is simpler operations. One update covers compute, storage and networking, and there is no separate storage product to monitor or keep on a compatibility list.
Legacy HCI sends I/O through a storage VM. VergeFS writes through the operating system itself.
Use the SAN Storage You Already Own
Most hyperconverged architectures require you to replace your current servers and storage before you see any benefit. VergeOS works with the hardware you have. Fibre Channel arrays contribute capacity directly to the VergeOS environment, where VergeFS adds its own resiliency, snapshots and deduplication on top.
- Fibre Channel arrays present storage directly to VergeOS
- Existing software-defined storage servers return to service as storage-only nodes
- Arrays retire on your schedule, not on a vendor refresh cycle
Arrays, storage-only nodes and compute nodes all contribute to one VergeFS pool.
Turn Server Drives into Shared Storage
VergeFS aggregates the internal drives of every node in a VergeOS instance into a single virtualized pool that all VMs share. Customers buy server-class drives at server prices instead of paying storage vendor markups, which reduces storage cost by 5X or more compared to dedicated arrays.
The VergeFS protocol talks directly to the Ethernet ports, so every link is active. There is no link aggregation to configure and no idle standby path.
- NVMe, SAS and SATA flash plus hard disk drives in the same instance
- Active-active use of every network port
- Capacity grows by filling open drive bays or adding nodes
Mixed flash and hard drives across nodes form one shared pool.
Keep Data Online Through Drive and Server Failures
VergeFS protects data from hardware failure and user error. Its integration into VergeOS keeps VMs running through a drive failure, a server failure, an accidental deletion or data corruption. When a drive fails, VergeFS serves the data from its redundant copy at the device level, with no rebuild delay for the application.
ioGuardian extends that protection. It keeps data online and repairs it inline when failures exceed the instance’s built-in redundancy, and it is included in VergeOS at no additional cost. See how the full stack handles high availability and disaster recovery.
A failed drive never stops the VM. Reads move to the redundant copy, and ioGuardian backs up the backup.
Deduplication That Helps the Whole Stack
In most environments, deduplication is a storage feature with little benefit to the hypervisor or the network. VergeFS runs deduplication inside VergeOS, so every layer benefits. Once a node identifies a redundant segment, that segment, other than its metadata, is never sent across the network or processed by another node. That saves CPU, memory and bandwidth on every server.
- Always on and inline
- About 5X reduction in capacity requirements
- Global awareness across the entire instance
Duplicates are removed on the first node. Only unique segments travel the network.
Eliminate Storage Refreshes
Dedicated arrays and legacy HCI force a forklift upgrade every four to five years. VergeFS grows instead. Add drives to open bays, add a storage-only node, or add a new server from a newer generation, and VergeOS adds the capacity to the same pool with no data migration project.
- Mix server vendors, generations and media types in one instance
- Scale storage and compute independently
- Per-server licensing, so growth never means counting cores
Capacity grows in place. No forklift upgrade and no migration project.
VergeFS Compared to Legacy vSAN
| Capability | Legacy vSAN and HCI storage | VergeFS in VergeOS |
|---|---|---|
| Architecture | Separate storage software or controller VM per server | Native service in the same code base as the hypervisor |
| Existing SAN arrays | Replaced during the HCI rollout | Fibre Channel arrays contribute capacity directly |
| Deduplication | Storage-only, often optional or tier-limited | Always on, inline and global across storage, compute and network |
| Snapshots | Limited count with a performance penalty | Unlimited ioClone snapshots with no performance impact |
| Media | Hardware compatibility list and matched nodes | NVMe, SAS, SATA flash and HDD across mixed servers |
| Licensing | Per core or per TB | Per server, all features included |
See What Your Data Center Looks Like on VergeOS
Tell us a little about your environment and a VergeIO engineer will create a free custom solution diagram. It shows how VergeOS and VergeFS fit your existing servers and storage, and which arrays and drives move into the pool.
Prefer to talk it through? Book a technical whiteboard session with our team.
Solution Architecture Diagram
Frequently Asked Questions About vSAN and VergeFS
What is a vSAN?
A vSAN, or virtual storage area network, pools the physical drives in multiple networked servers and presents them as one shared storage resource managed from a central console. Most vSAN products run as a virtual machine or a separate software module under the control of the hypervisor.
What is VergeFS?
VergeFS is the storage layer built into VergeOS. It pools server drives and existing Fibre Channel arrays into one shared resource, with no separate software package and no storage virtual machines.
How is VergeFS different from legacy vSAN technology?
VergeFS is part of the VergeOS operating system instead of a guest of the hypervisor. The hypervisor, network and storage share one code base, which shortens the I/O path, lowers overhead on every server and lets deduplication benefit the whole stack.
Does VergeFS support existing SAN storage?
Yes. Fibre Channel arrays contribute storage directly to the VergeOS environment, and existing software-defined storage servers can return to service as storage-only nodes.
What cost savings does VergeFS offer?
VergeFS virtualizes the internal drives of each node into a global pool, so customers buy server-class SSDs directly instead of paying storage vendor markups. VergeIO customers see storage costs drop by 5X or more compared to dedicated arrays or legacy vSAN.
How does VergeFS scale?
Capacity grows by filling open drive bays or adding nodes, including storage-only nodes. VergeFS supports NVMe, SAS and SATA flash plus hard disk drives across mixed server generations.
What is hypervisor-aware deduplication?
VergeFS runs inline, global deduplication inside VergeOS. Once a node identifies a redundant segment, that data is never sent across the network or processed by another node. Capacity requirements drop by about 5X, and CPU and network load drop with them.
How does VergeFS protect data?
VergeFS protects against hardware failure and user error. VMs keep running through drive or server failures, and ioGuardian keeps data online when failures exceed the built-in redundancy.
How does VergeFS handle drive failures?
VergeFS handles drive failures at the device level. It serves data from redundant segments with no extra processing, so applications keep running with minimal performance impact.
How are VergeFS snapshots different?
VergeFS uses ioClone. Each snapshot is a complete, independent copy of its source that consumes no additional capacity at creation. VergeFS supports unlimited snapshots with no performance penalty, which makes frequent, long-term retention practical.
Retire the Storage Silo, Keep the Hardware
VergeFS turns the servers and arrays you already own into one shared, deduplicated pool inside VergeOS. Try it yourself in the free hands-on labs or get a diagram built for your environment.