<?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 SnapDrive Account:  Required Filer Permissions in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapDrive-Account-Required-Filer-Permissions/m-p/58650#M5362</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've done some playing around with the SnapDrive account and discovered that it needs API-* capabilities to do what appears to be everything it needs to do.&amp;nbsp;&amp;nbsp; Is this true or am I missing something?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I'd like to restrict the volumes that are visible by the SnapDrive account running on a particular host.&amp;nbsp;&amp;nbsp; For example, I'd like to ensure that HOSTA only see's the volumes and luns specific to HOSTA.&amp;nbsp; HOSTA should not see the volumes/luns belonging to HOSTB or any of the NAS volumes on the filer.&amp;nbsp;&amp;nbsp; Is the SecureAccess.xml the only option for restricting the volume visibility of the SnapDrive account by host or is there something I can do through RBAC only (without using the SecureAccess.xml file)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jordan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:23:25 GMT</pubDate>
    <dc:creator>MRJORDANG</dc:creator>
    <dc:date>2025-06-05T06:23:25Z</dc:date>
    <item>
      <title>SnapDrive Account:  Required Filer Permissions</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapDrive-Account-Required-Filer-Permissions/m-p/58650#M5362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've done some playing around with the SnapDrive account and discovered that it needs API-* capabilities to do what appears to be everything it needs to do.&amp;nbsp;&amp;nbsp; Is this true or am I missing something?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I'd like to restrict the volumes that are visible by the SnapDrive account running on a particular host.&amp;nbsp;&amp;nbsp; For example, I'd like to ensure that HOSTA only see's the volumes and luns specific to HOSTA.&amp;nbsp; HOSTA should not see the volumes/luns belonging to HOSTB or any of the NAS volumes on the filer.&amp;nbsp;&amp;nbsp; Is the SecureAccess.xml the only option for restricting the volume visibility of the SnapDrive account by host or is there something I can do through RBAC only (without using the SecureAccess.xml file)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jordan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:23:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapDrive-Account-Required-Filer-Permissions/m-p/58650#M5362</guid>
      <dc:creator>MRJORDANG</dc:creator>
      <dc:date>2025-06-05T06:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: SnapDrive Account:  Required Filer Permissions</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapDrive-Account-Required-Filer-Permissions/m-p/58655#M5363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was able to use RBAC integrated with DFM to restrict users based on DFM groups.&amp;nbsp; This works great, and access is managed from DFM using accounts created to match the AD user accounts.&amp;nbsp; You can then create the necessary roles and assign the SD access rights.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Sep 2013 12:51:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapDrive-Account-Required-Filer-Permissions/m-p/58655#M5363</guid>
      <dc:creator>mike_burt</dc:creator>
      <dc:date>2013-09-17T12:51:43Z</dc:date>
    </item>
  </channel>
</rss>

