<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Move iSCSI Target Service in VMware vSAN Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Move-iSCSI-Target-Service/m-p/2963106#M15077</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1773180"&gt;@nitro_jawt&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I'm not sure if I fully understand your query. The active path for iSCSI to the I/O Owner of the iSCSI LUN will move across hosts automatically if needed - e.g. when entering maintenance mode for the host or during a failure. The owner is automatically decided by vSAN and cannot be manually influenced.&lt;/P&gt;&lt;P&gt;From a data perspective the iSCSI LUN is a vSAN object, which is split across the entire vSAN cluster as any other objects. You can't move the data of the object to a specific host, as there's also no need to.&lt;/P&gt;&lt;P&gt;-pk&lt;/P&gt;</description>
    <pubDate>Sun, 09 Apr 2023 10:55:41 GMT</pubDate>
    <dc:creator>pkvmw</dc:creator>
    <dc:date>2023-04-09T10:55:41Z</dc:date>
    <item>
      <title>Move iSCSI Target Service</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Move-iSCSI-Target-Service/m-p/2962189#M15055</link>
      <description>&lt;P&gt;Hi, have a client with a 6-node vSAN cluster providing iSCSI targets to some physical boxes. Generally works ok, but they want to be able to pro-actively move the services for specific iSCSI targets between nodes in the cluster for load-balancing and maintenance planning. Is there any way to do this at the moment? (It's all vSphere 7.03).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 07:10:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Move-iSCSI-Target-Service/m-p/2962189#M15055</guid>
      <dc:creator>nitro_jawt</dc:creator>
      <dc:date>2023-04-03T07:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: Move iSCSI Target Service</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Move-iSCSI-Target-Service/m-p/2963106#M15077</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1773180"&gt;@nitro_jawt&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I'm not sure if I fully understand your query. The active path for iSCSI to the I/O Owner of the iSCSI LUN will move across hosts automatically if needed - e.g. when entering maintenance mode for the host or during a failure. The owner is automatically decided by vSAN and cannot be manually influenced.&lt;/P&gt;&lt;P&gt;From a data perspective the iSCSI LUN is a vSAN object, which is split across the entire vSAN cluster as any other objects. You can't move the data of the object to a specific host, as there's also no need to.&lt;/P&gt;&lt;P&gt;-pk&lt;/P&gt;</description>
      <pubDate>Sun, 09 Apr 2023 10:55:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Move-iSCSI-Target-Service/m-p/2963106#M15077</guid>
      <dc:creator>pkvmw</dc:creator>
      <dc:date>2023-04-09T10:55:41Z</dc:date>
    </item>
  </channel>
</rss>

