Last week, I was rolling out Horizon View v7.1 on my new vSAN 6.6.1 all-flash configuration in the lab. Now, one of the pet peeves a few of us have had with this configuration was that a warning was always reported around read cache reservations on all-flash vSAN. Of course, read cache is irrelevant to all-flash (AF) configurations as it does not use a read cache; this is only applicable to hybrid vSAN configurations. This is why it was such as annoyance.
We are hearing about a number of VSAN stretched cluster implementations going on at the moment, which is great news. I just set up such a configuration once again in my lab as we look at some various scenarios for the next release of VSAN. Now, for anyone looking at implementing VSAN stretched cluster, there is the VSAN 6.1 stretched cluster guide which should be your first port of call. However I noticed that once VSAN stretched cluster is implemented, you get a few warnings that you typically wouldn’t see in standard VSAN deployments. That is what I want to…
A number of customers have experienced some issues with getting the Virtual SAN (VSAN) health check to work correctly in their environments. The most common issues have been permissions and certificates. In this post, I want to highlight these issues and any associated KB articles, and call out the symptom as well as the resolution.
With the announcements just made at VMworld 2015, the embargo on Virtual SAN 6.1 has now been lifted, so we can now discuss publicly some of the new features and functionality. Virtual SAN is VMware’s software-defined solution for Hyper-Converged Infrastructure (HCI). For the last number of months, I’ve been heavily involved in preparing for the Virtual SAN 6.1 launch. What follows is a brief description of what I find to be the most interesting and exciting of the upcoming features in Virtual SAN 6.1. Later on, I will follow-up with more in-depth blog posts on the new features and functionality.