What’s new in vSAN 6.7U1

Yesterday, we saw the announcement that VMware has release vSphere 6.7U1. This includes new releases of vCenter Server 6.7U1, ESXi 6.7U1 and of course vSAN 6.7U1. All of the hyperlinks here will take you to the release notes of that particular product. In this post, I just want to briefly run through some of the major enhancements that we have included in vSAN 6.7U1. TRIM/UNMAP Support Top of the list for me is the introduction of automated UNMAP support. Note that the key point here is that this is for in-guest space reclamation. vSAN has never had an issue with…

What’s in the vSphere and vSAN 6.7 release?

Today VMware unveils vSphere version 6.7, which also includes a new version of vSAN. In this post, I am going to highlight some of the big-ticket items that are in vSphere 6.7 from a core storage perspective, and also some of the new feature that you will find in vSAN 6.7. I’ll also cover some of the new enhancements coming in Virtual Volumes (VVols).

Guest OS space reuse on vSAN

This post came about after a brief discussion with my pal, Lee Dilworth. Although the outcome of this test has really nothing to do with vSAN, the behaviour was observed on certain Guest OS which were running on vSAN. I guess the first thing that needs to be made clear is that there is no support for in-guest UNMAP (or TRIM) for VMs running on vSAN at this time, although it is something we are examining very closely. So with this in mind, we had feedback to say that a test being run as part of a proof-of-concept was showing…

vSphere 6.5 p01 – Important patch for users of Automated UNMAP

VMware has just announced the release of vSphere 6.5 p01 (Patch ESXi-6.5.0-20170304001-standard). While there are a number of different issues addressed in the patch, there is one in particular that I wanted to bring to your attention. Automated UNMAP is a feature that we introduced in vSphere 6.5. This patch contains a fix for some odd behaviour seen with the new Automated UNMAP feature. The issue has only been observed with certain Guest OS, certain filesystems, and a certain block sizes format. KB article 2148987 for the patch describes it as follows: Tools in guest operating system might send unmap…

Determining if an array supports automated unmap in vSphere 6.5

Many of you will be aware of the new core storage features that were introduced in vSphere 6.5. If not, you can learn about them in this recently published white paper. Without doubt, the feature that has created the most amount of interest is automated unmap (finally, I hear you say!). Now a few readers have asked about the following comment in the automated unmap section. Automatic UNMAP is not supported on arrays with UNMAP granularity greater than 1MB. Auto UNMAP feature support is footnoted in the VMware Hardware Compatibility Guide (HCL). So where do you find this info in…

vSphere 6.5 Core Storage White Paper Now Available

I’m delighted to announce the availability of a new vSphere 6.5 core storage white paper. The paper covers new features such as VMFS-6 enhancements, policy driven Storage I/O Control, policy driven VM Encryption, NFS and iSCSI improvements and of course new limit increases in vSphere 6.5. There are too many VMware folks to thank for putting this paper together, but you’ll find them all listed in the acknowledgements section. I do want to mention one person however; a very special thanks to Cody Hosterman of Pure Storage who spent a lot of time testing many of these new features, and…

vSphere 6.0 Storage Features Part 8: VAAI UNMAP changes

A few weeks, my good pal Cody Hosterman over at Pure Storage was experimenting with VAAI and discovered that he could successfully UNMAP blocks (reclaim) directly from a Guest OS in vSphere 6.0. VAAI are the vSphere APIs for Array Integration. Cody wrote about his findings here. Effectively, if you have deleted files within a Guest OS, and your VM is thinly provisioned, you can tell the array through this VAAI primitive that you are no longer using these blocks. This allows the array to reclaim them for other uses. I know a lot of you have been waiting for…