<?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: SVM Root Volume on SAN SVM in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/129653#M28204</link>
    <description>&lt;P&gt;I have the same doubt, I created the LS mirrors at the end, just in case. As aborzenkov stated, the SVM need this volume to start.&lt;/P&gt;</description>
    <pubDate>Fri, 31 Mar 2017 10:01:02 GMT</pubDate>
    <dc:creator>DavidDAVE</dc:creator>
    <dc:date>2017-03-31T10:01:02Z</dc:date>
    <item>
      <title>SVM Root Volume on SAN SVM</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123463#M26445</link>
      <description>&lt;P&gt;I have read in the "SVM Root Volume Protection Express Guide" on page 4 that "SAN client connections (FC, FCoE, or iSCSI) do not depend on the SVM root volume". If that is true, is there any reason to protect the root volume for a totally SAN-based SVM? If there is an issue with the root volume on a SAN SVM, what are the consequences and how would you restore, if you didn't have root volume protection in place?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2016 20:43:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123463#M26445</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2016-09-21T20:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: SVM Root Volume on SAN SVM</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123471#M26449</link>
      <description>&lt;P&gt;I do not think you can start SVM if root volume is not available.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 06:49:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123471#M26449</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2016-09-22T06:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: SVM Root Volume on SAN SVM</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123486#M26456</link>
      <description>&lt;P&gt;I agree it's critical, I just wonder if I need to add to my snapmirror traffic by mirroring the root volume of SAN-based SVMs.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 13:58:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/123486#M26456</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2016-09-22T13:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: SVM Root Volume on SAN SVM</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/129653#M28204</link>
      <description>&lt;P&gt;I have the same doubt, I created the LS mirrors at the end, just in case. As aborzenkov stated, the SVM need this volume to start.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 10:01:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/SVM-Root-Volume-on-SAN-SVM/m-p/129653#M28204</guid>
      <dc:creator>DavidDAVE</dc:creator>
      <dc:date>2017-03-31T10:01:02Z</dc:date>
    </item>
  </channel>
</rss>

