vSAN 6.7 U1 Deep Dive book now available in Traditional Chinese

A very short post to highlight to my Asian readers that the vSAN 6.7 U1 Deep Dive book has now been translated into Traditional Chinese by Taiwanese company DrMaster. If you are interested in picking up a copy, we have been provided with the following links to web sites where you can purchase the book. This is opportune timing, as VMware has only just announced the newest release of vSAN, version 6.7 U3. Here are the links provided by DrMaster to online book stores in Asia where the book can be found. Tenlong Computer Books. This is the most famous…

Celebrating 20,000 #vSAN Customers – Thank you

Wow – more than 20,000 vSAN customers. What an amazing journey it has been. If you haven’t seen it, vSAN license bookings grew over 50% year-over-year in Q1 with a total customer count growing to over 20,000 (seekingalpha.com). Now we need to keep the pace and, as Duncan put it, remain the number 1 player in the hyperconverged and hybrid cloud world! As a sort of thank you to everyone who helped make this happen,  Duncan and I have decided to lower the price of our vSAN Deep Dive book for 1 week. So, until Friday, June 7th, we have…

A first look at the Couchbase Operator

A few weeks back, I took a look at Heptio Velero, formely known as Ark. Velero provides backup and restore capabilities for cloud native applications. During that research, I used a Couchbase DB as my application of choice for backup/restore. After speaking to Couchbase regarding that blog post, they strongly recommended I try the new Couchbase operator rather than the StatefulSet method that I was using for the application. Couchbase talk about the advantages of the operator approach over StatefulSets here. Now, while Couchbase provide steps on how to deploy Couchbase with their operator, they create it in the default…

Fun with PKS, K8s, MongoDB Helm Charts and vSAN

I’ve been spending a bit of time lately look at our Heptio Velero product, and how it works with various cloud native applications. Next application on my list is MongoDB, another NoSQL database. I looked at various deployment mechanisms for MongoDB, and it seems that using Helm Charts is the most popular approach. This led me to the Bitnami MongoDB Stack Chart GitHub Repo. At this point, I did spin my wheels a little trying to get MongoDB stood up. In this post, I’ll talk through some of the gotchas I encountered. Once again, my environment is vSphere 6.7 and…

New vRealize Automation, Cloud Assembly integration with SPBM

At VMworld last year, Duncan Epping and I presented on the power of Storage Policy Based Management (SPBM for short). You can find all of the slides and recordings here. One of the demos we used in the presentation was deploying virtual machines via vRealize Automation, and showing how to consume a storage policy on vSAN. This was using a vRealize Automation plugin, and to be honest, it was a little bit challenging to get it to work. And it wasn’t really a VMware plugin per-se, but something developed by our field team. Today, I’m pleased to announce that we…

Degraded Device Handling (DDH) Revisited

Degraded Device Handling (DDH) or Dying Disk Handling as it was formerly known, is a feature that has been available in vSAN for some time. However, I regularly get questions about how it works. The DDH behavior has changed significantly over various versions. We may as well begin this post with an overview about the purpose of DDH and then get into the different sort of behaviors. First of all, the reason behind a feature such as DDH is to help avoid cluster performance degradation due to an unhealthy drive. In the early days of vSAN, we had come across…

vSAN Erasure Coding Failure Handling

I had a very interesting question recently about how vSAN handles a failure in an object that is running with an erasure coding configuration. In the case of vSAN this is either a RAID-5 or a RAID-6. On vSAN, a RAID-5 is implemented with 3 data segments and 1 parity segment (3+1), with parity striped across all four components. RAID-6 is implemented as 4 data segments and 2 parity segments (4+2), again with the parity striped across all of the six components. Now, on vSAN, RAID-5 requires 4 physical ESXi hosts for implementation, with each host backing one set of…