Skip to main content

Key New vSAN Features in VMware Cloud Foundation (VCF 9.0)


The release of VMware Cloud Foundation (VCF 9.0) brings one of the most significant evolutions in vSAN to date—delivering performance, efficiency, and flexibility enhancements tailored for today’s demanding workloads. With data growth accelerating and enterprises embracing AI, analytics, and hybrid cloud strategies, storage platforms must do more than just store bits—they must accelerate innovation, protect critical assets, and optimize resource usage.

In VCF 9, vSAN introduces breakthrough capabilities like cluster-wide global deduplication, native vSAN-to-vSAN replication with deep, immutable snapshots, and major data path performance optimizations. Combined with ESA’s blistering IOPS performance, advanced memory tiering, and greater storage architecture flexibility, these features address modern enterprise needs ranging from AI/ML pipelines to cyber-resilient disaster recovery.

In this article, we’ll explore the most impactful new vSAN features in VCF 9, why they matter for architects and IT leaders, and how they can transform your cloud foundation into a future-ready storage powerhouse.

Global Deduplication


  • vSAN ESA in VCF 9.0 introduces software-based, cluster-wide deduplication that identifies and removes redundant 4KB blocks across the entire cluster, not just per disk group, significantly improving data reduction efficiency.
  • The deduplication engine is post-process and opportunistic, running in the background using free CPU cycles to minimize impact on foreground workloads and latency.
  • Broadcom states potential storage reduction up to 8x, depending on data characteristics, materially shrinking storage footprint and lowering overall TCO.
  • The feature is available with vSAN ESA in VCF 9.0 P01 and, at launch, has specific scope and limitations (e.g., limited availability via RPQ/approved requests and environmental prerequisites)


vSAN-to-vSAN Replication with Deep Snapshots

  • VCF 9.0 adds native, asynchronous vSAN-to-vSAN replication built on vSAN Data Protection, enabling remote replication of vSAN snapshots to any vSAN ESA datastore (HCI or disaggregated).
  • Replication supports immutable, crash-consistent deep snapshots with histories up to 200 snapshots per-VM, enabling cyber recovery workflows that can roll back to clean points in time.


  • Integration with VMware Live Recovery provides full DR orchestration, low RPOs (as low as 1 minute), simplified lifecycle with a single appliance, and more efficient failover/failback at the VM level instead of array LUNs.

Enhanced Data Path Performance

  • VCF 9.0 includes platform networking and data path enhancements, including options for NSX Enhanced Data Path that can deliver up to 3x switching performance, lowering latency and CPU overhead for high-throughput workloads.


  • These enhancements benefit chatty microservices and data-intensive pipelines by reducing network bottlenecks and improving end-to-end throughput.

Support for Modern AI and Memory-Intensive Workloads

  • vSAN ESA continues to deliver up to 300,000 IOPS per node with consistent sub-millisecond latency, with performance and capacity scaling linearly as the cluster grows, aligning to AI/ML and other latency-sensitive workloads.


  • Advanced Memory Tiering (vSphere feature in VCF 9) is production-ready and improves effective memory capacity and consolidation via DRAM–NVMe tiering, increasing CPU utilization and VM density for memory-heavy applications.

Flexible Management Domain Storage

  • In VCF 9.0, organizations gain flexibility to use alternative primary storage for the Management Domain beyond vSAN, such as FC or NFS, aligning storage choices with existing investments and operational preferences.

Improved Storage Cluster Networking

  • Storage cluster networking can be separated from compute networking in VCF 9.0, enabling independent optimization of network resources and better utilization of existing network infrastructure for compute traffic.

Why These Matter

  • Global dedupe reduces storage cost without materially affecting performance, especially valuable at scale and with redundant datasets typical in VMs and container images.
  • Native vSAN replication with deep, immutable snapshots plus Live Recovery orchestration enables granular VM-level cyber/disaster recovery with deeper restore points and faster, simpler recovery paths than array/LUN workflows.


  • Data path and networking gains, combined with ESA’s high IOPS/low-latency profile and memory tiering, support modern AI/ML and microservice workloads with predictable performance at scale.

Notes for my fellow Architects

  • Global dedupe is ESA-only and cluster-wide; plan capacity and CPU headroom for background post-process operations and confirm environmental prerequisites during early adoption phases.
  • For cyber recovery, align snapshot retention (up to 200 per VM) with ransomware dwell-time assumptions and integrate with isolated recovery environments via Live Recovery where sovereignty requires on-premises recovery.
  • Consider networking separation and NSX Enhanced Data Path to reduce contention and achieve higher throughput for storage and east–west application traffic.

 

If you found this article informative, please share it within your team for further knowledge sharing.....

Labels:
Location: Bengaluru, Karnataka, India

Comments

Post a Comment

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with...
2 comments
Read more

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0 ...
2 comments
Read more

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
Post a Comment
Read more