<?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: Understanding SimpliVity File System - VM Files And Storage vMotion in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/understanding-simplivity-file-system-vm-files-and-storage/m-p/7022565#M142</link>
    <description>&lt;P&gt;Here is a set of links that explains the answer to your question. They explain it better than I can. The important thing to remember is that VMware has no idea what SimpliVity is doing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/07/20/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster/" target="_blank"&gt;https://damianerangey.com/2018/07/20/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;2-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/08/29/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-2/" target="_blank"&gt;https://damianerangey.com/2018/08/29/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;3-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/09/14/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-3/" target="_blank"&gt;https://damianerangey.com/2018/09/14/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-3/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;4-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/10/16/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-4/" target="_blank"&gt;https://damianerangey.com/2018/10/16/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-4/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you read these you will have a pretty good idea what goes on in the mind of a SimpliVity cluster-&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Oct 2018 01:55:46 GMT</pubDate>
    <dc:creator>MikeSeden</dc:creator>
    <dc:date>2018-10-22T01:55:46Z</dc:date>
    <item>
      <title>Understanding SimpliVity File System - VM Files And Storage vMotion</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/understanding-simplivity-file-system-vm-files-and-storage/m-p/7022100#M135</link>
      <description>&lt;P&gt;Good Evening Everyone,&lt;/P&gt;&lt;P&gt;I am little confused on how and more important - where - the VM files (VMX and VMDK files) are stored in a Simplivity cluster. I have a basic understanding of the SimpliVity DVP system and its Object Store and how it presents a NFS file system to ESXi 6.5 hypervisor. I understand how data is updated in metadata vs new information, etc&lt;/P&gt;&lt;P&gt;What I am missing here is where are the files stored? Is a VM and its files stored entirely on the node regardless of a selected datastore, or are the VM "scattered" across nodes in a cluster.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second - how does storage vMotion work in a SimpliVity cluster. Let's suppose we have a two node SimpliVity cluster daisy changed together via 10GB connect. Let's say on node 1 do a storage vMotion from a NFS Simplivity datastore1 to another NFS Simplivity datastore2.&amp;nbsp; &amp;nbsp; Does this mean that files are moved between nodes?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Steve&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Oct 2018 01:15:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/understanding-simplivity-file-system-vm-files-and-storage/m-p/7022100#M135</guid>
      <dc:creator>shandy4473</dc:creator>
      <dc:date>2018-10-17T01:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding SimpliVity File System - VM Files And Storage vMotion</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/understanding-simplivity-file-system-vm-files-and-storage/m-p/7022565#M142</link>
      <description>&lt;P&gt;Here is a set of links that explains the answer to your question. They explain it better than I can. The important thing to remember is that VMware has no idea what SimpliVity is doing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/07/20/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster/" target="_blank"&gt;https://damianerangey.com/2018/07/20/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;2-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/08/29/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-2/" target="_blank"&gt;https://damianerangey.com/2018/08/29/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;3-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/09/14/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-3/" target="_blank"&gt;https://damianerangey.com/2018/09/14/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-3/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;4-&amp;nbsp;&lt;A href="https://damianerangey.com/2018/10/16/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-4/" target="_blank"&gt;https://damianerangey.com/2018/10/16/how-virtual-machine-data-is-stored-and-managed-within-a-hpe-simplivity-cluster-part-4/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you read these you will have a pretty good idea what goes on in the mind of a SimpliVity cluster-&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 01:55:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/understanding-simplivity-file-system-vm-files-and-storage/m-p/7022565#M142</guid>
      <dc:creator>MikeSeden</dc:creator>
      <dc:date>2018-10-22T01:55:46Z</dc:date>
    </item>
  </channel>
</rss>

