<?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 Minimum SnapCenter Permissions in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/451732#M43476</link>
    <description>&lt;P&gt;For years we've used a custom role for SnapCenter permissions on our iSCSI and NFS SVMs, based on the following article:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.netapp.com/t5/Data-Backup-and-Recovery/SnapCenter-Custom-Account-ONTAP/m-p/156197#M12840" target="_blank"&gt;https://community.netapp.com/t5/Data-Backup-and-Recovery/SnapCenter-Custom-Account-ONTAP/m-p/156197#M12840&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This has worked well. Now I'm testing to add the new snapshot locking feature in OnTAP 9.12.1 so I can lock the three most recent snapshots from deletion. In testing, my custom role is generating "Insufficient privileges" alerts, stating the custom account "does not have write access to this resource". The specific failed task was "Set SnapLock Expiration Time Failed".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the following KB article and added the two additional actions listed to the role, but got the same error. Any suggestions? I really want to implement this, but this permission issue is turning into a blocker.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/dp/SnapLock/Unable_to_set_retention_at_file_level" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/dp/SnapLock/Unable_to_set_retention_at_file_level&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 09:39:41 GMT</pubDate>
    <dc:creator>TMADOCTHOMAS</dc:creator>
    <dc:date>2025-06-04T09:39:41Z</dc:date>
    <item>
      <title>Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/451732#M43476</link>
      <description>&lt;P&gt;For years we've used a custom role for SnapCenter permissions on our iSCSI and NFS SVMs, based on the following article:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.netapp.com/t5/Data-Backup-and-Recovery/SnapCenter-Custom-Account-ONTAP/m-p/156197#M12840" target="_blank"&gt;https://community.netapp.com/t5/Data-Backup-and-Recovery/SnapCenter-Custom-Account-ONTAP/m-p/156197#M12840&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This has worked well. Now I'm testing to add the new snapshot locking feature in OnTAP 9.12.1 so I can lock the three most recent snapshots from deletion. In testing, my custom role is generating "Insufficient privileges" alerts, stating the custom account "does not have write access to this resource". The specific failed task was "Set SnapLock Expiration Time Failed".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the following KB article and added the two additional actions listed to the role, but got the same error. Any suggestions? I really want to implement this, but this permission issue is turning into a blocker.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/onprem/ontap/dp/SnapLock/Unable_to_set_retention_at_file_level" target="_blank"&gt;https://kb.netapp.com/onprem/ontap/dp/SnapLock/Unable_to_set_retention_at_file_level&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:39:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/451732#M43476</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2025-06-04T09:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/451874#M43502</link>
      <description>&lt;P&gt;For anyone watching this thread, I have a case open and will hopefully have an answer from NetApp Support soon.&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2024 14:16:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/451874#M43502</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2024-04-09T14:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452442#M43582</link>
      <description>&lt;P&gt;From what we discovered in the case, the rule doesn't work in 9.12.1 but should work in later versions. We are postponing implementation of this feature until we decide to upgrade.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2024 19:34:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452442#M43582</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2024-04-30T19:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452452#M43585</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you speaking of the general "Minimum Privileges" feature which doesn't work with 9.12.1 or just the new Snaplock feature?&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2024 08:05:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452452#M43585</guid>
      <dc:creator>isc-dario</dc:creator>
      <dc:date>2024-05-01T08:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452458#M43588</link>
      <description>&lt;P&gt;The feature itself works, it's just the tweaking of minimum permissions that doesn't work in 9.12.1.&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2024 12:53:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452458#M43588</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2024-05-01T12:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452462#M43589</link>
      <description>&lt;P&gt;Have you tried the minimum permissions before enabling the Snaplock feature?&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2024 14:41:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452462#M43589</guid>
      <dc:creator>isc-dario</dc:creator>
      <dc:date>2024-05-01T14:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: Minimum SnapCenter Permissions</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452463#M43590</link>
      <description>&lt;P&gt;No, however it was weird that the NetApp technician who worked with me was able to make it work in 9.13.1 and above without changes to the rules. Meaning there wasn't actually a rule change to make, although I thought there was and tried a few that I thought would work when it initially failed. Apparently something behind the scenes was tweaked in 9.13.1 and above. At any rate, I'll revisit when we upgrade later this fall.&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2024 14:53:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Minimum-SnapCenter-Permissions/m-p/452463#M43590</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2024-05-01T14:53:28Z</dc:date>
    </item>
  </channel>
</rss>

