VSAN 6.2Finally, it’s here!. Today VMware announced the release of Virtual SAN 6.2. This version qualifies as pinnacle release of Virtual SAN because of all of the new data services and capabilities included in the product.

  • Deduplication and Compression
  • RAID5/RAID6
  • Enhanced Health Services
  • Performance Metrics
  • Quality of Service – IOPS Limits
  • Sparse Swap Files
  • In Memory Read Caching
  • Software Checksum

If one combines the new data services announced today with the ones available with the current 6.1 release, you have a feature rich storage platform that is designed and capable of meeting the requirements of today’s most demanding enterprise applications.

While all of the data services are significant from a technology and value proposition standpoint, I would like to point out one of the most important facts about them, and that is the way in which they were designed and implemented to work together with other features and components of the Virtual SAN architecture.

By nature, some of these data services are very expensive from a resource consumption perspective. They are traditionally found in dedicated hardware arrays where certain processes and resource demands are offloaded to dedicated hardware components. That type of implementation doesn’t work in today’s Software-Defined Storage and Hyper-Converged Infrastructure architectures. In Hyper-Converged infrastructures, all of the available resources (Compute, Network, Storage) are shared between infrastructure data services and applications (Virtual Machines).

With Hyper-Converged Infrastructures, the ideal scenario would be to utilized the necessary data services without consuming a significant amount of the available resources or contending for resources that are meant to be consumed by an application (Virtual Machines).

In Virtual SAN, the data services were strategically designed and optimized to work together in a Software-Defined stack to deliver their efficiency values without introducing an overwhelming resource overhead. For example Deduplication and compression work together, in the event a workload is not suited for deduplication, then perhaps Compression may be of help, and vice versa. Also, RAID-5/6 (Erasure Coding) guarantees storage resource savings without compromising on data availability.

For example:

  • Deduplication and compression work together, in the event a workload is not suited for deduplication, then perhaps Compression may be of help, and vice versa.
  • Also, RAID-5/6 (Erasure Coding) guarantees storage resource savings without compromising on data availability.

These are necessary architectural and implementation changes required for a reliable Software-Defined Storage platform that aligns with today’s economics for Hyper-Converged Infrastructures. This cannot be done with the data service implementations that are based on old our outdated infrastructure architectures.

In an industry driven by products that claim to be Software-Defined Solutions, there is only one platform that I know provides customers with the ability to configure Software-Defined Availability, Software-Defined Performance, Software-Defined Space Efficiencies settings, etc. All of these consumable capabilities can be individually applied to any application or object (Virtual Machine or Disks) and are provided through storage policy management framework (SPBM) and that platform is Virtual SAN.

VSAN6.2-Policy_

I believe it’s time to look at Virtual SAN as more than just an another storage solution, and put into perspective the operational efficiencies such as infrastructure agility, risk mitigation, and increased manageability that it delivers. If you haven’t done it yet, test Virtual SAN and take a closer look and see for yourself.

The year just started, there is a whole lot more where that came from…..

-Enjoy

For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds.

X