• 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

vcf

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,

#108 – My Explore recap: VCF Native S3 Object Storage, Cyber Recovery, and vSAN on FC!

Duncan Epping · Dec 1, 2025 · Leave a Comment

I had some difficulties scheduling guests the past weeks due to my travel schedule, and as a result, I figured I would try something new. In this episode, I go over the various things I announced at Explore and Explore on Tour in London, Paris, and Frankfurt. I talk about VCF Native S3 Object Storage, the enhancements we are planning for Disaster Recovery as well as Cyber Recovery, and I also briefly touch on vSAN on FC.

You can listen to my solo episode, episode 108, on Spotify (bit.ly/3MxRyZC), Apple Podcasts (bit.ly/4iEM5ML), or via the embedded player on Yellow-Bricks below.

If you like to hear more about vSAN ESA Global Deduplication, make sure ⁠to go to this blog on Yellow-Bricks⁠, as it contains the links to the discussion Pete Koehler and I had on the show a while back. I also just published the demo I recorded for Explore on Youtube, make sure to watch that one!

I also had Jatin Jindal on the show a month or two ago to discuss all Ransomware/Cyber Recovery enhancements in-depth. You can listen to that episode via Spotify (bit.ly/3IWQCwz), Apple (bit.ly/4o6YVoG), or via the embedded player on yellow-bricks.com!

#107 – Why VCF is the best platform for your modern workloads featuring Jad El-Zein!

Duncan Epping · Nov 17, 2025 · Leave a Comment

Recently, I read this article about why VCF is the best platform for modern workloads, so I figured I would invite the author, Jad El-Zein. Jad and I discuss all the arguments of why VCF and all components are the perfect destination for containers, or I should probably say your modern workloads. You can listen to the episode on Apple Podcast (bit.ly/4nXIs5y), Spotify (bit.ly/3K7mj6W), or just use the embedded player below.

What do I do after a vSAN Stretched Cluster Site Takeover?

Duncan Epping · Nov 10, 2025 · 4 Comments

Over the last couple of months, various new vSAN features were announced. Two of those features are around the Stretched Cluster configuration, and have probably been the number 1 feature request for a few years. Now that we have Site Takeover and Site Maintenance functionality available, I am starting to get some questions about the impact of them, and in particular, the Site Takeover functionality is raising some questions.

For those who don’t know what these features are, let me describe them briefly:

Site Maintenance = The ability to place a full vSAN stretched cluster Fault Domain into maintenance mode at once. This ensures that all hosts within the fault domain have consistently stored the data, and all hosts will go into maintenance mode at the same time.

Site Takeover = This provides the ability when a Witness and a Data Site has failed to bring back the remaining site through a command line interface. This will reconstruct the remaining “site local” RAID configuration, making the objects available again, which will then allow vSphere HA to restart the VMs.

Now, the question that the above typically raises is what happens to the Witness and the Data Site that failed when you do the Site Takeover? If you look at the VMs RAID configuration, you will notice that both the Witness and the Data Site components of the sites that failed will completely disappear from the RAID configuration.

But what do you do next, because even after you run the Site Takeover, you still see your hosts and the witness in vCenter Server, and you still see a stretched cluster configuration in the UI. Now at first I thought that if the environment was completely up and running again, you had to go through some manual effort to reconstruct the stretched cluster. Basically, remove the failed hosts, wipe the disks, and recreate the stretched cluster. This is, however, not the case.

In the example above, if the Preferred site and the Witness site return for duty, vSAN will automatically discard the stale components in those previously failed sites. It will recreate new components for all objects, and it will do a full resync of the data.

If you end up in a situation where your hosts are completely gone (let’s say as a result of a fire), then you will have to do some kind of manual cleanup as follows, before you rebuild and add hosts back:

  • Remove the failed hosts from the vCenter inventory
  • Remove the witness from the vCenter inventory
    • Delete the witness from the vCenter Server it is running, a real delete!
  • Delete the surviving Fault Domain, this should be the only Fault Domain still listed in the vCenter interface
  • You now have a normal cluster again
  • Rebuild hosts and recreate the stretched cluster

I hope that helps,

  • Page 1
  • Page 2
  • Page 3
  • 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