<?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: OnTap RBAC for VSC @ Snapmirror Destination in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/OnTap-RBAC-for-VSC-Snapmirror-Destination/m-p/45926#M4515</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jim, you should give the RBAC User Creator tool (communities.netapp.com/docs/DOC-19074) a try.&amp;nbsp;&amp;nbsp; It will simplify your life ... at least when it pertains to creating RBAC user names!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Aug 2013 19:25:31 GMT</pubDate>
    <dc:creator>dbkelly</dc:creator>
    <dc:date>2013-08-19T19:25:31Z</dc:date>
    <item>
      <title>OnTap RBAC for VSC @ Snapmirror Destination</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/OnTap-RBAC-for-VSC-Snapmirror-Destination/m-p/45922#M4514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looking through the KB, there are a number of RBAC privs that need to be listed.&amp;nbsp; As I try to work with a customer who is using VSC at their site, am wondering what the minimum perms are needed at the snapmirror destination site.&amp;nbsp; Outside of the requirement for api-snapmirror-update &amp;amp; login-http, am wondering if all the others are actually required for the backup/recovery user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are more perms here than I wish to actually turn over, as an example: api-igroup-destroy, api-lun-unmap, api-nfs-exportfs-appen-rules-2 &amp;amp; api-nfs-exportfs-modify-rule-2, api-snapshot-delete, api-snapshot-rename, api-system-cli, api-volume-destroy, api-volume-offline, cli-ifconfig&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can see why some of these would be needed at the primary site, but at the destination - only if they also have abilities to spin up the VMs and the destination side ESX hosts are in the same vCenter - not the case in our environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Goal:&amp;nbsp; Allow for the customer to use VSC Backup &amp;amp; Recovery at their site without issue (don't want errors to show up because of restrictions at the destination), allow for the customer to execute a snapmirror update.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:55:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/OnTap-RBAC-for-VSC-Snapmirror-Destination/m-p/45922#M4514</guid>
      <dc:creator>JIM_SURLOW</dc:creator>
      <dc:date>2025-06-05T05:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: OnTap RBAC for VSC @ Snapmirror Destination</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/OnTap-RBAC-for-VSC-Snapmirror-Destination/m-p/45926#M4515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jim, you should give the RBAC User Creator tool (communities.netapp.com/docs/DOC-19074) a try.&amp;nbsp;&amp;nbsp; It will simplify your life ... at least when it pertains to creating RBAC user names!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Aug 2013 19:25:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/OnTap-RBAC-for-VSC-Snapmirror-Destination/m-p/45926#M4515</guid>
      <dc:creator>dbkelly</dc:creator>
      <dc:date>2013-08-19T19:25:31Z</dc:date>
    </item>
  </channel>
</rss>

