What’s New in vSAN 6.7 Update 1

posted

VMware vSAN is the market leader in HCI. One of the many driving forces that has helped solidify this position, is the rapid and continuous pace of innovation. VMware has always given customers the power of choice, and this continues into the hybrid cloud era. VMware’s digital foundation gives customers the ability, and flexibility to Read more...

More vSAN Cmdlets in PowerCLI 11!

posted

There’s a new release of PowerCLI, and it includes some more vSAN goodness! We’ve added some capabilities previously found in the Ruby vSphere Console and have also updated a couple of the existing modules   The new and updated cmdlets include: Get-VsanObject makes it easy to get information about a vSAN Object or a VM’s Read more...
Mixed MTU

Understanding Mixed MTU support in Stretched & 2 Node vSAN 6.7 U1 clusters with Witness Traffic Separation

posted

Witness Traffic Separation introduced the ability to tag “witness” traffic on an alternate VMkernel interface on vSAN data nodes. Witness Traffic Separation is the feature that enabled 2 Node “Direct Connect” in vSAN 6.5, and was also added to later editions of vSAN 6.2 (vSphere 6.0 Update 3 & higher). Some additional logic was added Read more...

Using SPBM Policies to Manage Your Virtual Volumes

posted

  In the first of the SPBM series, we talked about Tag based Storage Policy Based Management (SPBM). Next, in the series, we will review how you can manage Virtual Volumes (VVols) using SPBM. If you are unfamiliar with VVols, take a look at Storagehub for an overview and more details on what and how Read more...
Witness Consolidation

Understanding vSAN Witness Consolidation & 2 Node vSAN

posted

The vSAN Witness Appliance was introduced as a free alternative to using a physical ESXi host as a vSAN Witness Host. This appliance is only used for housing vSAN Object Witness Components, and is not allowed to run any virtual machine workloads. When deploying the vSAN Witness Appliance, there are 3 potential deployment options: Tiny, Read more...
UNMAP - "Because no ones wants to play storage Jenga(TM)"

VMware vSAN 6.7U1 Storage reclamation – TRIM/UNMAP

posted

VMware vSAN supports thin provisioning, which lets you, in the beginning, use just as much storage capacity as currently needed and then add the required amount of storage space at a later time. Using the vSAN thin provisioning feature, you can create virtual disks in a thin format. For a thin virtual disk, vSAN provisions Read more...

GreyBeards HCI podcast with Lee Caswell

posted

GreyBeards  published podcast with Lee Caswell,  discussing HCI stack , Edge computing, and vVol adoption. It is a great timing – as VMworld is just a few days away and it provides key takeaways to discuss at the event. Here are the key topics discussed by Lee: HCI operates at the edge – with ROBO-2-server environments, VMware’s Read more...

Better Together: Site Recovery Manager (SRM) and Virtual Volumes (VVol)

posted

Recently there has been a lot of interest in VMware’s Virtual Volumes (VVols) technology as our shared- storage customers begin to understand the value of deploying vSphere policy-based storage management.  As our customers have become more experienced with VVols, many have started to ask how they can implement business continuance and disaster recovery solutions using Read more...
vSAN Encryption

Understanding vSAN Encryption – KMS Profile Addressing

posted

When using vSAN Encryption, one of the vSAN Health Check tests will show the health of the connection between the vSAN Hosts and the KMS Cluster as well as vCenter and the KMS Cluster. One scenario came up a few weeks ago where the vSAN Health Check indicated that the vSAN Hosts could properly communicate Read more...
traditional datastores

Understanding vSAN – Can it be used with Traditional or VVol Storage?

posted

On a call today this question came up: “Can vSAN be used with other storage?” This is a very common question, covered in the vSAN FAQ on storagehub.vmware.com, as well in other publicly facing VMware.com documentation. The answer is an absolute YES! A vSAN Cluster can also use traditional datastores and/or use VVols. Why wouldn’t this be supported? Read more...