Supported CloudPoint operations on NetApp NAS models
You can perform the following CloudPoint operations supported on the NetApp models:
Table: CloudPoint operations on the NetApp array
CloudPoint operations | Description |
|---|---|
Discover assets | CloudPoint discovers all the NAS volumes using the active junction path on the NetApp storage. Junction-Path specifies the access protocol for either NFS or SMB. |
Create snapshot | CloudPoint takes a snapshot of the NetApp NFS and SMB share using volume. When a snapshot is triggered on the NetApp storage using NetBackup, a REST API is called to creates a snapshot of the volume. A typical snapshot created by CloudPoint have the following naming convention: NB<unique_21digit_number>. |
Delete snapshot | CloudPoint deletes the snapshot of the NAS volume. |
Restore snapshot | When you restore a volume from a snapshot, CloudPoint only restores the volume on which the restore is triggered. The volume snapshot restore, restores a snapshot copy to the read-write volume. Replacing the current copy of the volume with the snapshot copy. Results, loss of all changes made since the snapshot copy was created. Note: If restore operation is performed on the older snapshots then, all the latest snapshots captured are deleted as a part of NetApp behavior and the latest snapshot cannot be restored. |
Export snapshot | When a snapshot export operation is triggered, for NFS, export policy rules are checked for source volume. If the export rules matches the client (selected in the policy) which includes protocol as NFS or SMB or both with superuser access. Then the backup is performed directly on the client. If no export rule match is found then a new rule with NFS protocol, read-only with superuser access is created in the export policy and is assigned to the export snapshot. For SMB protocol, a new share is created with read permission which includes the path of the snapshot. This share name is created with name with snapshot name prefix. Example: NB<unique_21digit_number>-432464523 |
Deport snapshot | When a snapshot deport operation is triggered, for SMB CloudPoint deletes the shares created during export call. For NFS, no action is performed. |
On the clustered Data ONTAP SnapDiff RPC API V2 is supported from ONTAP release 9.4 onwards till ONTAP 9.9.
You must enable SnapDiff RPC service on the SVM. Follow the steps:
controller> vserver snapdiff-rpc-server on <svm_name>
For more information, refer to the NetApp documentation for latest and accurate methods to enable snapdiff-rpc-server.
To improve performance while fetching the SnapDiff data between two snapshots, max_diffs and max_sessions must be set on the filer.
By default, SnapDiff RPC API V2 max_diff is set to 256 and max_sessions are set to 16.
Max limit for max_diff is 4096 and max_sessions is 64.
To set max_diffs and max_sessions on the filer
- Set max_diff limit to 4096
controller> node run -node options replication.spinnp.snapdiff.max_diffs 4096
- Set max_session limit to 64
controller> node run -node options replication.spinnp.snapdiff.max_sessions 64
For more information, refer to the NetApp documentation for latest and accurate methods to set max_diffs/max_sessionsto,
To configure ACL on NetApp array follow the steps:
- Log onto the OnCommand System Manager.
- Go to the respective SVM where the SMB volume is created.
- Click right on the SVM setting.
- On the left click the Windows under Host Users and Groups. The Groups and Users tabs are displayed.
- In the Groups tab, click the BUILTIN\Backup Operators and select Edit option.
- In the Modify dialog, under the Members section, add the domain user and select the SetBackupPrivilege, SetRestorePrivilege, and SetSecurityPrivilege privileges.
In NetApp NAS deployment, NetBackup discovers all the NFS and SMB shares using volumes NAS path on the NetApp storage.
Also, discovers the NetApp Storage Virtual Machines (SVMs) from which the NFS and SMB shares are created to mount.