Skip to main content

Introducing VMware vSAN 8.0: New Features and Enhancements Unveiled


VMware vSAN 8.0 brings forth a range of exciting features and enhancements, aiming to revolutionize storage architecture and elevate performance. 

Let's explore the key highlights of this major release and discover how it improves scalability, usability, and overall efficiency.

1) vSAN Express Storage Architecture (ESA):

VMware introduces vSAN Express Storage Architecture (ESA) as an alternative to the original storage architecture (OSA). ESA presents a cost-effective and scalable solution specifically designed for edge and remote deployments. 

It employs a streamlined, single-tier architecture, where all devices contribute to storage capacity. This eliminates the need for disk groups with caching devices, simplifying deployment and reducing costs.

2)Native Snapshots with Minimal Performance Impact:

vSAN ESA now offers native snapshots that have minimal impact on virtual machine (VM) performance, even with deep snapshot chains. These snapshots seamlessly integrate with existing backup applications utilizing VMware VADP, ensuring smooth and efficient data protection.

3) Enhanced Compression Capabilities:

vSAN ESA introduces improved compression capabilities, delivering up to four times better compression. The compression process occurs prior to data transmission across the vSAN network, resulting in enhanced bandwidth utilization and optimized storage efficiency.

4) Expanded Usable Storage Potential:

By leveraging the single-tier architecture, vSAN ESA eliminates the necessity for disk groups with caching devices. This design shift can boost usable storage capacity by up to 20%, providing greater flexibility and resource utilization.

5) HCI Mesh Support for 10 Client Clusters:

vSAN 8.0 extends support for HCI Mesh by enabling the sharing of a storage server cluster with up to 10 client clusters. This advancement simplifies deployment and management of large-scale vSAN infrastructures, promoting efficiency and ease of use.

Additional Performance and Usability Enhancements:

  • Improved performance for sequential writes on vSAN ESA.
  • Optimized I/O processing for single VMDK/objects on vSAN ESA.
  • Enhanced durability in maintenance mode scenarios on vSAN ESA.
  • Increased administrative storage capacity on vSAN datastores using customizable namespace objects.
  • Witness appliance certification for vSAN 8.0 Update 1

"VMware vSAN 8.0 represents a significant milestone, introducing a host of features and enhancements that enhance performance, scalability, and usability. With its innovative vSAN Express Storage Architecture, native snapshots, improved compression, expanded storage potential, and HCI Mesh support, vSAN 8.0 empowers organizations to leverage cutting-edge technology for their storage needs. Upgrade to vSAN 8.0 to unlock the full potential of your virtualized infrastructure."


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 the

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@ Here, the URL specified is the ESXi host ( under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)

Removing NSX-T manager extension from vCenter

In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform. As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager. Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T. Lets get started.. 1) Login to NSX-T UI Go to -> System ->Compute Manager Here, vCenter is showing in Down status where the status is showing as "Not Registered" 2) When we click on "Not Registered" option its states below error. 3) When try to click on Resolve option its states below. At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter. To remove the NSX-T e