• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Can I replicate, or snapshot, my vSAN Stretched Cluster Witness appliance for fast recovery?

Duncan Epping · Jan 20, 2026 · Leave a Comment

I’ve been seeing this question pop up more frequently, can I replicate or snapshot my vSAN Stretched Cluster Witness appliance for fast recovery? Usually, people ask this question as they cannot adhere to the 3-site requirement for a vSAN Stretched Cluster. So by setting up some kind of replication mechanism with low RPO, they try to mitigate this risk.

I guess the question stems from a lack of understanding of what the witness does. The witness provides a quorum mechanism, the quorum mechanism helps determine which site has access to the data in the case of a network failure (ISL) between the data locations.

Can I replicate, or snapshot, my vSAN Stretched Cluster Witness appliance for fast recovery?

So why can the Witness Appliance not be snapshotted or replicated then? Well, in order to provide this quorum mechanism, the Witness Appliance stores a witness component for each object. This is not per site, or per VM, but for every object… So if you have a VM with multiple VMDKs, you will have multiple witness objects per VM stored on the witness appliance. That witness object holds metadata and, through a log sequence number, understands which object holds the most recent data. This is where the issue arises. If you revert a Witness Appliance to an earlier point in time, the witness components also revert to an earlier point in time, and will have a different log sequence number than expected. This results in vSAN being unable to make the object available to the surviving site, or the site that is expected to hold quorum.

So in short, should you replicate or snapshot the Witness Appliance? No!

 

#110 – vSAN over Fibre Channel featuring Rakesh Radhakrishnan!

Duncan Epping · Jan 19, 2026 · 3 Comments

After Rakesh and I shared the news at Explore, and Explore On Tour, that vSAN would potentially be able to use Fibre Channel as a transport layer, the phone has been ringing nonstop. It was time for me to invite Rakesh and ask him to explain what vSAN over FC is all about. In this episode Rakesh covers the why, the what, but unfortunately the when is still a question. Nevertheless, this episode is a must-listen or watch, as I decided to also make it available on youtube this time. Pick what you prefer! Listen on Spotify (https://bit.ly/3YMdlzP), Apple (https://apple.co/45OncsI), or listen via the embedded player below, or just click the video!

Discussed papers/links:

  • ⁠vSAN vs Traditional Storage video⁠
  • ⁠vSAN beats all-flash top storage system

Playing around with Memory Tiering, are my memory pages tiered?

Duncan Epping · Dec 18, 2025 · 1 Comment

There was a question on VMTN about Memory Tiering performance, and how you can check if pages were tiered. I haven’t played around with Memory Tiering too much, so I noted down for myself what I needed to do on every host in order to enable it. Note, if the command contains a path and you want to do this in your own environment you need to change the path and device name accordingly. The question was if memory pages were tiered or not, so I dug up the command that allows you to check this on a per host level. It is at the bottom of this article for those who just want to skip to that part.

Now, before I forget, probably worth mentioning as this is something many people don’t seem to understand, memory tiering only tiers cold memory pages. Active pages are not being moved to NVMe, on top of that, it only tiers memory when there’s memory pressure! So if you don’t see any tiering, it could simply be that you are not under any memory capacity pressure. (Why move pages to a lower tier when there’s no need?)

List all storage devices via the CLI:

esxcli storage core device list

Create memory tiering partition on an NVMe device:

esxcli system tierdevice create -d=/vmfs/devices/disks/eui.1ea506b32a7f4454000c296a4884dc68

Enable Memory Tiering on a host level, note this requires a reboot:

esxcli system settings kernel set -s MemoryTiering -v TRUE

How is Memory Tiering configured in terms of DRAM to NVMe ratio? A 4:1 DRAM to NVMe ratio would be 25%, 1:1 would be 100%. So if you have it set at 4:1, with 512GB of DRAM you would only use 128GB of the NVMe at most, regardless of the size of the device.

esxcli system settings advanced list -o /Mem/TierNvmePct

Is memory tiered or not? Find out all about it via memstats!

memstats -r vmtier-stats -u mb

Want to show a select number of metrics?

memstats -r vmtier-stats -u mb -s name:memSize:active:tier1Target:tier1Consumed:tier1ConsumedPeak:comnsumed

So what would the outcome look like when there is memory tiering happening? I removed a bunch of the metrics, just to keep it readable, “tier1” is the NVMe device, and as you can see each VM has several MBs worth of memory pages on NVMe right now.

 VIRTUAL MACHINE MEMORY TIER STATS: Wed Dec 17 15:29:43 2025
 -----------------------------------------------
   Start Group ID   : 0
   No. of levels    : 12
   Unit             : MB
   Selected columns : name:memSize:tier1Consumed

----------------------------------------
           name    memSize tier1Consumed
----------------------------------------
      vm.533611       4096            12
      vm.533612       4096            34
      vm.533613       4096            24
      vm.533614       4096            11
      vm.533615       4096            25
----------------------------------------
          Total      20480           106
----------------------------------------

#109 – Introducing Virtual Private Cloud (VPC) featuring Yves Hertoghs

Duncan Epping · Dec 15, 2025 · Leave a Comment

VMware Cloud Foundation 9 has brought the ⁠Virtual Private Cloud networking model⁠ front and center in the vSphere UI. Not only has it become extremely easy to provide a self-service solution for networking, but it also comes with a plethora of networking services and capabilities. Maybe even more importantly, it allows networking-noobs (like myself) to consume advanced functionality without having to file dozens of service requests. In this episode, Yves Hertoghs explains what a Virtual Private Cloud is and discusses all the ins and outs around the Transit Gateway, vDefend, subnets, and much more.

You can listen to the episode on Spotify (bit.ly/3MArJs9), Apple Podcasts (bit.ly/3YtUhWQ), or online via the embedded player below.

If you like to learn more about VPCs, make sure to read the various blogs, and watch the various Explore sessions on the topic. There’s plenty out there to dive straight into it!

  • Blog: VPCs in vCenter

  • Blog: Self-Service Networking with Virtual Private Clouds

  • Blog – VPC Distributed Network Connectivity – No NSX Edge VMs

  • Explore Video: Easily set up networking in vCenter with VPC — watch it live in action

  • Explore Video: Virtual Private Cloud Zero to Hero: Mastering Private Cloud Networking

Plenty of things to read and watch during the upcoming holiday season, I am going to take a short break as well, but I will be back in January for sure! Enjoy,

vSAN to vSAN Replication and Recovery Plan creation demo!

Duncan Epping · Dec 9, 2025 · Leave a Comment

As I was going through the various recordings I had of demos I created for Explore, I realized I hadn’t published the demos I created for vSAN to vSAN Replication, and on creating a Recovery Plan based on a vSAN Protection Group in VMware Live Recovery. So here it is. It is a pretty lengthy video as I go through all the various steps involved. So what you will see in this demo is the following:

  • vCenter Server Pairing between my 2 sites
  • Cluster pairing
  • Creation of a vSAN Protection Group, including vSAN to vSAN Replication
  • Creation of a Recovery Plan based on the previously created Protection Group
  • Test of the Recovery Plan

  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 495
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Also visit!

For the Dutch-speaking audience, make sure to visit RunNerd.nl to follow my running adventure, read shoe/gear/race reviews, and more!

Do you like Hardcore-Punk music? Follow my Spotify Playlist!

Do you like 80s music? I got you covered!

Copyright Yellow-Bricks.com © 2026 · Log in