After being asked about how vSphere Host Groups worked with Availability Zones in Enterprise PKS earlier this week, I decided to spend a little time setting it up in my lab and doing some testing to make sure I could understand the feature and its behaviour. Essentially what this feature allows you to do is […]
Category: stretched cluster
Most readers will be aware that vSAN version 6.7U1 was recently released. For those of you who wish to know more about the release, I wrote this blog article last month detailing the new features. In this post I want to cover an item which many of you may not be aware of. It is […]
This question has come up a number of times in the past. However, there have been some updates that I personally was not aware of until last week. To cut to the chase, Horizon View 7 (all clone types) is supported with vSAN stretch cluster. This is good news. However, it is very important that […]
I was with one of our large EMEA customers last week, and we talked quite a bit about the evolution of vSAN. This customer is already one of our larger vSAN customers with very many clusters, and many, many nodes. They have also been a great vSAN reference for us, having first deployed the initial […]
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 […]
Many of you who are well versed in vSAN will realize that we released a Secondary Failures To Tolerate (SFTT) feature with vSAN 6.6. This meant that not only could we tolerate failures across sites, but that we could also add another layer of redundancy to each copy of the data maintained at each of […]
After publishing the vSAN Networking Guide earlier this year, Paudie O’Riordain and I received numerous questions regarding support on having different stretched clusters hosting each other’s witness appliances. These queries arose because we discussed a 2-node (ROBO) topology which allowed this to sort of configuration (i.e. the cross hosting of witnesses) via special request. But […]