Catch me at Cisco Live EMEA 2017 – Berlin

Later on this month, I will be attending my first Cisco Live event. This year, it is taking place in Berlin, Germany. As part of the event, I have the opportunity to deliver a 20 minute presentation on vSAN. The session is titled “Architectural Overview of HCI powered by VMware”. Many of you will already be aware that vSAN is currently VMware’s fastest growing product. In this session, I will give an architectural overview of vSAN. The hope is to teach some of the basic principles behind vSAN, as well as many of its features. I will also talk about…

Another recovery from multiple failures in a vSAN stretched cluster

In a previous post related to multiple failures in a vSAN stretched cluster, we showed that if a failure caused the data components to be out of sync, the most recent copy of the data needs to recover before the object becomes accessible again. This is true even if there are a majority of objects available (e.g. old data copy and witness). This is to ensure that we do not recover the “STALE” copy of the data which might have out of date information. To briefly revisit the previous post,  the accessibility of the object when there are multiple failures…

Understanding recovery from multiple failures in a vSAN stretched cluster

Sometime back I wrote an article that described what happens when an object deployed on a vSAN datastore has a policy of Number of Failures to Tolerate set to 1 (FTT=1), and multiple failures are introduced. For simplicity, lets label the three components that make up our object with FTT=1 as A, B and W. A and B are data components and W is the witness component. Let’s now assume that we lose access to component A. Components B & W are still available, and the object (e.g. a VMDK) is still available. The state of these two components (B…

The continued rise of HCI, and especially vSAN

This morning, twitter is alive with VMware’s Q4 2016 results. In a nutshell, its been a phenomenal quarter. Of course, the first thing I wanted to check out was how vSAN did. “Outstanding” is the word. At VMworld 2016 in Barcelona, we were somewhere around 5,500 vSAN customers. Today, that number stands at 7,000. In the space of a year we have more than doubled the number of vSAN customers globally. There is no doubt about it, but Hyper-Convergence is hot. The recent acquisition of SimpliVity by HPE demonstrates this. [Update] As does NetApp’s intention of getting into the HCI…

New vSAN Management Pack for vRealize Operations

Last month we announced the release of a new vROps Management Pack specifically for vSAN. Previously the vSAN Management Pack was bundled with the MPSD – Management Pack for Storage Devices. I wrote about this when it entered beta, way back in 2015. Well, for those customers who are only interested in monitoring vSAN, and didn’t want all the other parts of the MPSD, the new vSAN Management Pack is now a stand-alone offering, so no MPSD required. This new vSAN Management Pack focuses on 3 main areas of vSAN: (1) Health and Availability, (2) Performance Analysis and (3) Capacity…

vSAN Stretched Cluster – Partition behavior changes

My good pal Paudie and I are back in full customer[0] mode these past few weeks, testing out lots of new and upcoming features in future release of vSAN. Our testing led us to building a new vSAN stretched cluster, with 5 nodes on the preferred site, 5 nodes on the secondary site, and of course the obligatory witness node. Now, it had been a while since we put vSAN stretched cluster through its paces. The last time was the vSAN 6.1 release, which led us to create some additional sections on stretched cluster for the vSAN Proof Of Concept…

Gathering core dump files when encryption is enabled

One of the key new features of vSphere 6.5 is vSphere VM Encryption, a mechanism to encrypt all virtual machine files. This mechanism not only encrypts the VMDK, but also the metadata files and core dumps associated with a VM. Now, there would not be much point in sending an encrypted core dump file to VMware for analysis, so a mechanism has been put in place to allow these files to be recrypted using a password before sending them to VMware. The password can then be shared with VMware to allow us to examine the core dumps.  This is how…