As with any vSphere launch, there are a bunch of new storage related features announced. This year is a little different as there are some considerable updates which I wanted to share with you.
Virtual SAN (VSAN)
VMware has made a public beta announcement on VSAN. While it is not yet GA, it is almost there and vSphere 5.5 will enable you to try it out first hand. VMware is taking a software-defined approach with VSAN and providing a product that is radically simpler, more scalable and agile, and lower-cost than traditional monolithic SAN or NAS storage. The storage is flexible & elastic in that virtual storage can live anywhere across the pooled resource. It’s inherently a fault-replace model; any failure is handled without downtime. And, the entire system is tightly integrated with, and automated by, vCenter … and it’s specifically integrated into the application provisioning workflow so that it’ll maximize Cloud application deployment agility. There will be a lot more on VSAN over the coming weeks and months – stay tuned.
vSphere Flash Read Cache
vFRC is a hypervisor-based software-defined flash storage tier solution. It aggregates local flash devices to provide a clustered flash resource for consumption by both virtual machines and ESXi hosts. ESXi hosts can consume the flash via Virtual Flash Host Swap Cache (what used to be known as swap to SSD in previous vSphere releases).
Virtual Machine are allocated a part of the flash resource via the web client. The flash is allocated on a per VMDK basis. vFRC is a write-thru caching mechanism in this initial release, which means that the writes go directly to persistent storage as well as into cache, which means that the block is available for subsequent reads to be accelerated.
62TB VMDKs and vRDMs
Yes, we finally have VMDKs that can grow to a size larger than the 2TB – 512 bytes. And we also have 62TB virtual mode RDMs (non pass thru). This is great to see, and something I know a lot of you have been waiting for. Why 62TB and not 64TB I hear you ask? Well, 64TB is still the maximum size of the VMFS-5 datastore, so if you filled the VMFS datastore with a single VMDK, there would be no space left for certain management tasks, like taking a snapshot, etc. This was problematic in the past when we had 2TB VMFS extents and 2TB VMDKs. So lesson learnt, and we have left some overhead.
There are some considerations when using 62TB VMDKs as you might well imagine, but I will cover those in a future post.
16Gbit FC E2E Support
In vSphere 5.0, VMware introduced support for 16Gb FC HBAs. However these HBAs had to be throttled down to work at 8Gb. In 5.1, we supported these HBAs running at 16Gb but there was no support for full end-to-end 16Gb connectivity from host to array. The host to switch could run at 16Gb, but the switch to array had to run at 8Gb. With the release of vSphere 5.5, VMware now supports 16Gb E2E (end-to-end) Fibre Channel connectivity.
Microsoft Cluster Services Enhancements
In 5.1, we introduced support for 5 node clusters running on vSphere. In 5.5, we have a number of additional changes. First off, VMware now supports FCoE and iSCSI protocols for shared disk access. Up until now, this has been supported on Fibre Channel only. We have also introduced support for the round robin path policy on the shared disks. And finally, support for Microsoft Windows 2012 support has also been introduced. A lot of enhancements in this area.
I’m not going to delve back into the history of All Paths Down (APD) or Permanent Device Loss (PDL). This has a long and checkered history, and has been extensively documented. Suffice to say that this situation occurs on device failures or if the device is incorrectly removed from host. PDL is based on SCSI Sense Codes returned from the array and a PDL state means that the ESXi host no longer sends I/O to these devices.
PDL AutoRemove in vSphere 5.5 automatically removes a device with PDL from the host. A PDL state on a device implies that the device is gone and that it cannot accept more IOs, but needlessly uses up one of the 256 device per host limit. PDL AutoRemove gets rid of the device from the ESXi host perspective.
VAAI UNMAP Improvements
vSphere 5.5 introduced a new simpler VAAI UNMAP/Reclaim command
# esxcli storage vmfs unmap
This is a big improvement from the older vmkfstools -y method. There are some additional enhancements to the reclaim mechanism too. The reclaim size now specified in blocks rather than a percentage value to make it more intuitive to calculate. Finally, dead space reclaimed in increments rather than all at once. Previously, trying to do reclaim in increments would have unmap trying to reclaim the same space over and over again. Lastly, with the introduction of 62TB VMDKs, unmap can now handle much larger dead space areas.
VMFS Heap Improvements
An issue with previous versions of VMFS heap meant that there were concerns when accessing above 30TB of open files from a single ESXi host. ESXi 5.0p5 & 5.1U1 introduced a larger heap size to deal with this. vSphere 5.5 introduces a much improved heap eviction process, meaning that there is no need for the larger heap size, which consumes memory. vSphere 5.5 with a maximum of 256MB of heap allows ESXi hosts to access all address space of a 64TB VMFS.
Storage DRS, Storage vMotion & vSphere Replication Interop
If a VM which was being replicated via vSphere Replication was migrated to another datastore, it triggered a full sync because the persistent state files (psf) were deleted – all of the disks contents are read and check summed on each side. In vSphere 5.5 the psf files are now moved with the virtual machine and retain its current replication state. This means that virtual machines at the production site may now be Storage vMotion’ed, and conversely, participate in Storage DRS datastore clusters without impacting vSphere Replication’s RPO (Recovery Point Objective).
Get notification of these blogs postings and more VMware Storage information by following me on Twitter: @VMwareStorage