<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VSAN-ESA on blogs.hareeshkg.com</title>
    <link>https://blogs.hareeshkg.bid/categories/vsan-esa/</link>
    <description>Recent content in VSAN-ESA on blogs.hareeshkg.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © blogs.hareeshkg.com 2025 reserved</copyright>
    <lastBuildDate>Tue, 20 Jun 2023 18:11:08 +0000</lastBuildDate><atom:link href="https://blogs.hareeshkg.bid/categories/vsan-esa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Native vSAN Trace Object</title>
      <link>https://blogs.hareeshkg.bid/post/native-vsan-trace-object/</link>
      <pubDate>Tue, 20 Jun 2023 18:11:08 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/native-vsan-trace-object/</guid>
      <description>
        
          
            &lt;p&gt;vSANTraces are generally used to troubleshoot and debug critical performance issues in vSAN(OSA and ESA) and also in some cases they are used to troubleshoot vSAN data-path related problems such as Stuck-IO, Congestion, slow/no de-stage etcetera. vSANTraces are not require to troubleshoot/debug all kinds of issues however is required for certain cases.&lt;/p&gt;
&lt;p&gt;In any vSAN enabled host, you might have noticed that the default location/path where the traces are collected is “/vsantraces”. Depending on the requirement, users may however change the path for vSANTraces to external Storage or a local datastore and change the default settings of “Number Of Files To Rotate:” and “Maximum Trace File Size:” for vSANTraces using esxcli commands. Having said that VMware doesnt recommend/allow customers to set the path for vSANTraces to vSAN-Datastore directly because it will impact performance of the virtual machines running on vSANDatastore as vsanTraces are write heavy (every subsystem of vSAN data-path writes to traces for bunch IO) which helps engineering to debug issues.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>vSAN-ESA SPBM and Compoment placements</title>
      <link>https://blogs.hareeshkg.bid/post/vsan-esa-spbm-and-compoment-placements/</link>
      <pubDate>Fri, 03 Mar 2023 09:48:49 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/vsan-esa-spbm-and-compoment-placements/</guid>
      <description>
        
          
            &lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;vSAN-ESA has introduced this concept of Storage Pools where all the disks in a given storage-pool contributes towards total capacity available for consumption. This initial release of vSAN ESA supports compression and encryption however doesn’t support Deduplication. vSAN ESA also introduced this concept of a log structured file System a.k.a LFS which I had discussed about briefly in my previous blog post, see &lt;a href=&#34;https://blogs.hareeshkg.bid/post/my-take-on-vsan-esa/&#34;&gt;My-take-on-ESA&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;When creating objects on vSAN-ESA datastore, the &lt;strong&gt;initial allocated space&lt;/strong&gt; for each object by default is &lt;strong&gt;3X the size of the object&lt;/strong&gt; +** 2% of the Object Size**.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>vSAN ESA – Log Structured File System</title>
      <link>https://blogs.hareeshkg.bid/post/vsan-esa-log-structured-file-system/</link>
      <pubDate>Thu, 12 Jan 2023 12:51:40 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/vsan-esa-log-structured-file-system/</guid>
      <description>
        
          
            &lt;p&gt;I have already briefly talked about vSAN-ESA’s Log Structured File System(LFS)  in my previous &lt;a href=&#34;https://blogs.hareeshkg.bid/vsan-esa-2&#34;&gt;blog&lt;/a&gt;, it advised to go over it once before you continue reading here.&lt;/p&gt;
&lt;p&gt;This blog talks about the overview and architecture of LFS and how erasure coding is benefited when LFS was introduced into vSAN ESA architecture.&lt;/p&gt;
&lt;h2 id=&#34;how-lfs-works&#34;&gt;How LFS works?&lt;/h2&gt;
&lt;p&gt;LFS in vSAN-ESA is responsible to handle all the incoming I/Os(Reads and Write) and acknowledge as fast as possible to the guest.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>My take on vSAN-ESA</title>
      <link>https://blogs.hareeshkg.bid/post/my-take-on-vsan-esa/</link>
      <pubDate>Thu, 22 Dec 2022 09:55:19 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/my-take-on-vsan-esa/</guid>
      <description>
        
          
            &lt;p&gt;vSAN-8 launched with a brand new storage architecture for vSAN called VMware vSAN Express Storage Architecture or ESA along side with a few enhancements to vSAN-OSA which is the Original Storage Architecture.&lt;/p&gt;
&lt;p&gt;Users are given an option at the beginning of vSAN Cluster setup with vSphere-8 to choose either  of the architecture, in this blog I explain what are the key features and enhancements of vSAN ESA and how it compares to OSA.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
