Limitations for the Network Share IntelliSnap Backup for NFS Exports

Consider the following limitations for the Network Share IntelliSnap Backup feature.

Limitations for Snapshot Operations

The name of the NFS export cannot contain a space.
For NFS snapshots, the GUI mount operation is not supported at storage policy copy or array levels.

Note

For Dell EMC Isilon/PowerScale NFS Exports, NFS Alias is not supported. However, you can use an Export path.

Wildcards are supported on the subclient content (non-automount) with Commvault indexing 2 only.
IntelliSnap backup of the default subclient is supported with Commvault indexing 2 only.
Leaf-level wildcards are not supported. For example, if /Dep1 directory contains content in folder1 to folder5 then specifying server1:/Dep1/folder[1-5] does not include any content from folder1 to folder5.

For NFS exports, there is no support for folders under the share path or under the share name as subclient content. Use the share path or share name.
Mount NFS exports on the client computer and use the share path or share name. If the share path and share name are different, use the share name to mount the NFS exports.
The revert operation is not supported.
For Huawei arrays with Snap Changelist support, if spool copy retention is set:
- Differential backup job may run as full.
- Data aging needs to run after backup copy job to age the snap jobs.

The junctions between volumes are not supported.
For the NetApp storage arrays with SnapDiff support if spool copy retention is set:
- Differential backup job may run as full.
- Data aging needs to run after backup copy job to age the snap jobs.
For the NetApp storage arrays with IntelliSnap support, wild cards are supported on the NFS automount shares.
For the NetApp C-Mode system, use individual Storage Virtual Machine (SVM) clients for NFS management. Do not use NetApp cluster for NFS snapshot management.

For the Dell EMC Isilon/PowerScale storage arrays with Snap Changelist support if spool copy retention is set: