<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Whats New? on blogs.hareeshkg.com</title>
    <link>https://blogs.hareeshkg.bid/categories/whats-new/</link>
    <description>Recent content in Whats New? on blogs.hareeshkg.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © blogs.hareeshkg.com 2025 reserved</copyright>
    <lastBuildDate>Sun, 08 Dec 2019 02:37:07 +0000</lastBuildDate><atom:link href="https://blogs.hareeshkg.bid/categories/whats-new/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WSFC with Native Shared Disks on vSAN</title>
      <link>https://blogs.hareeshkg.bid/post/wsfc-with-native-shared-disks-on-vsan/</link>
      <pubDate>Sun, 08 Dec 2019 02:37:07 +0000</pubDate>
      
      <guid>https://blogs.hareeshkg.bid/post/wsfc-with-native-shared-disks-on-vsan/</guid>
      <description>
        
          
            &lt;p&gt;With introduction of  vSAN 6.7 U3 / vSphere 6.7 U3  we now have native support for SCSI-3 Persistent reservation on vSAN objects. This means that we no longer need vSAN iSCSI targets for creating  &lt;strong&gt;a&lt;/strong&gt;pplication level clustering services like Windows Server Failover Clusters (WSFC) which needs to share a disk in order to determine ownership across the application cluster.&lt;/p&gt;
&lt;p&gt;This new feature allows for VMs running WSFC to use a shared VMDK on a vSAN datastore  by creating SCSI controllers in physical Mode and then create and share vmdks using independent-persistent presentation mode. This drastically reduces the time in deployment and configuration on WSFC when compared to previous vSAN releases which requires us to configure thru vSAN iSCSI targets and also comes with its overhead .&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
