Requirements for Using NetApp Snapdiff on Amazon FSxN File Servers

If you want to use NetApp SnapDiff for faster incremental backups, verify that your environment meets the system requirements.

System Requirements

For system requirements for MediaAgents as proxy computers, read the following topics:
- For system requirements for indexing, see System and Hardware Requirements.
- For system requirements for MediaAgents, see MediaAgent: System Requirements.
For system requirements for the file system agents, read the following topics:
- For the Linux file system agent, see System Requirements for Linux File Servers.
- For the Windows file system agent, see System Requirements for Windows File Servers.

Requirements in the Commvault Software

You must create subclients with Commvault FR 11.23 or a more recent release.
You must enter array credentials for the array. See Editing the User Credentials or Description of a Storage Array.

Ports

For snapshot-based operations, open port 443 (HTTPS) for communication between the NetApp server and CommServe computer, MediaAgent, access node or remote snapshot MediaAgent in your CommCell environment.
For SnapDiff V2, open port 2049 (NFS) for communication between the NetApp server and CommServe computer, MediaAgent, access node, or remote snapshot MediaAgent in your CommCell environment to transfer the file list information over NFS.
For SnapDiff V2, open port 111 from both Windows and Linux access nodes for the CIFS and NFS backups respectively.

Configuration Requirements for SnapDiff V2

Verify RPC is enabled on the vServer being cataloged or backup copied. Even if a cluster client is being cataloged, the vServer for the volume being cataloged or backup copied must have RPC enabled. On the file server, verify RPC is enabled on the vServer using the following commands:
```
set advanced
```
```
vserver snapdiff-rpc-server show -vserver $[vserver]
```
```
vserver snapdiff-rpc-server on -vserver $[vserver]
```
Verify whether an NFS interface exists between the vServer and the Commvault MediaAgent. Specifically, confirm that there exists a vServer NFS interface on the file server node containing the volume being cataloged using the following commands:
```
vserver nfs show -vserver $[vserver]
```
```
network interface show -vserver $[vserver] -data-protocol $[nfs]
```

Enable REST API based authorization

To enable REST API based authorization to the cluster array, run the following commands:

vserver services web access show -vserver $[vserver] -name $[rest] -role $[role]

vserver services web access create -vserver $[vserver] -name $[rest] -role $[role]

Use a non-root user to configure NetApp C-Mode Vserver

For the C-Mode system, to configure the array with a non-root user, type the following commands on the Vserver only:

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "vserver" \-access $[readonly]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[job show]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[lun]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[network interface]" \-access $[readonly]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[snapmirror]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[version]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[volume]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[volume efficiency]" \-access $[none]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[volume move]" \-access $[none]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver cifs]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver export-policy]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver fcp]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver fpolicy]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver iscsi]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver nfs]" \-access $[all]

security login role create \-vserver $[vserver_name] \-role $[IntelliSnap Role] \-cmddirname "$[vserver services ndmp]" \-access $[all]

security login create \-user\-or\-group\-name $[IntelliSnap User] \-application $[ontapi] \-authmethod $[password] \-role $[IntelliSnap Role] \-vserver $[vserver_name]

security login create \-user\-or\-group\-name $[IntelliSnap User] \-application $[ssh] \-authmethod $[password] \-role $[IntelliSnap Role] \-vserver $[vserver_name]

security login create -vserver $[vserver_name] -user-or-group-name $[IntelliSnapUser] -application $[http] -authentication-method $[password] -role $[IntelliSnapRole]

vserver services web access create -vserver $[vserver_name] -name $[rest] -role $[IntelliSnapRole]

security login unlock -username $[IntelliSnapUser] -vserver $[vserver_name]