<?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 Best practices for new storage FAS 8000 implementation in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Best-practices-for-new-storage-FAS-8000-implementation/m-p/127501#M27615</link>
    <description>&lt;P&gt;We have receiving Net app filer 4 node cluster. It supports 80TB and we are&amp;nbsp;separating for Finance data, HR Data, Engineering data, Public data separately and workloads for SAN boot for ESXI data. We are enabling ISCSI, FCOE, NFS shares and CIFS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need a &amp;nbsp;best practices before implementing this filer in our organization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Which is best options to Design for non-disruptive operations during upgrades and Power event failure in case of two nodes failure (All the times data should accesable).&lt;/LI&gt;&lt;LI&gt;All storage is managed by storage Admins so is it recommended to create single VSM? Or different VSM for different teams like HR, Finance etc,&lt;/LI&gt;&lt;LI&gt;Is recommended to create single aggregate or multiple aggregates for different teams.&lt;/LI&gt;&lt;LI&gt;Is recommended to create aggregate based Protocol we used like FC, NFS, ISCSI separately.&lt;/LI&gt;&lt;LI&gt;For performance perspective I need ESXI boot to be more fasters I have around 10x2TB SSD drives out 80TB Raw size .&lt;/LI&gt;&lt;LI&gt;Enabling Snapshots&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Wed, 04 Jun 2025 16:09:19 GMT</pubDate>
    <dc:creator>SagarDH</dc:creator>
    <dc:date>2025-06-04T16:09:19Z</dc:date>
    <item>
      <title>Best practices for new storage FAS 8000 implementation</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Best-practices-for-new-storage-FAS-8000-implementation/m-p/127501#M27615</link>
      <description>&lt;P&gt;We have receiving Net app filer 4 node cluster. It supports 80TB and we are&amp;nbsp;separating for Finance data, HR Data, Engineering data, Public data separately and workloads for SAN boot for ESXI data. We are enabling ISCSI, FCOE, NFS shares and CIFS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need a &amp;nbsp;best practices before implementing this filer in our organization.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Which is best options to Design for non-disruptive operations during upgrades and Power event failure in case of two nodes failure (All the times data should accesable).&lt;/LI&gt;&lt;LI&gt;All storage is managed by storage Admins so is it recommended to create single VSM? Or different VSM for different teams like HR, Finance etc,&lt;/LI&gt;&lt;LI&gt;Is recommended to create single aggregate or multiple aggregates for different teams.&lt;/LI&gt;&lt;LI&gt;Is recommended to create aggregate based Protocol we used like FC, NFS, ISCSI separately.&lt;/LI&gt;&lt;LI&gt;For performance perspective I need ESXI boot to be more fasters I have around 10x2TB SSD drives out 80TB Raw size .&lt;/LI&gt;&lt;LI&gt;Enabling Snapshots&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 04 Jun 2025 16:09:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Best-practices-for-new-storage-FAS-8000-implementation/m-p/127501#M27615</guid>
      <dc:creator>SagarDH</dc:creator>
      <dc:date>2025-06-04T16:09:19Z</dc:date>
    </item>
  </channel>
</rss>

