MENU
StarWind VVols for VMware vSphere Environment
Posted by Dmytro Malynka on June 16, 2017
No ratings yet.

Introduction

VMDK file to LUN storage architecture has been the most usable scenario for years until VMware released Virtual Volumes in vSphere 6.0. In the case of an array with block access, own VMware file system – VMFS  – was used -, and NFS was used for file storage. The array capacity was divided into LUNs or NFS-shares and presented ESXi hosts in the datastore form. Frequently, datastore is a large capacity storage housing numerous VMs. In fact, allocating a separate datastore for each VM is quite inconvenient and time-consuming in terms of administration.

With this approach, the VM storage maintenance operations are at the datastore level, and not at the Virtual Machine level. The operations like snapshots, replication, deduplication, encryption, etc. are performed at the storage level, thus being implemented faster with no use of compute and networking resources. The traditional VM storage technology described in vSphere is still supported. At once, Virtual Volumes (VVols) is an object containing VM files virtual disks and their derivatives.

This handy and at the same time advanced technology was integrated with StarWind Products, that I am about to implement.

StarWind Virtual SAN setup window

Learn More

Please rate this