NetBackup™ Snapshot Manager for Data Center Administrator's Guide
- Introduction
- Installation and Upgrade
- Configure NetBackup Snapshot Manager storage array plug-ins
- Storage array replication
- Storage array plug-ins for Snapshot Manager for Data Center
- Dell EMC PowerFlex array
- Dell EMC PowerMax and VMax array
- Dell EMC PowerScale (Isilon)
- Dell EMC PowerStore NAS array
- Dell EMC PowerStore SAN array
- Dell EMC XtremIO SAN array
- Dell EMC Unity array
- FUJITSU AF/DX array
- HPE RMC plug-in
- HPE XP SAN Storage array
- Hitachi NAS array
- Hitachi SAN array
- IBM Storwize array
- InfiniBox SAN array
- NetApp storage array
- Nutanix Files array
- Pure Storage Flash array
- Pure Storage FlashBlade NAS array
- Qumulo NAS array
- Configuring storage lifecycle policies for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Retention types for storage lifecycle policy operations
- Troubleshooting
Nutanix Files plug-in considerations and limitations
The following considerations and limitations are applicable:
Snapshot operations are not supported for nested shares on Nutanix Files File Server. A nested share is a share that is itself a subdirectory in an existing file share. NetBackup does not support snapshot creation for such nested shares.
Nutanix Files File Server does not support point-in-time (PIT) rollback restore of shares using snapshots. You can use NetBackup assisted restore of shares' data.
The maximum snapshot limit for a Nutanix Files share is 20. The maximum snapshot limit defines the maximum number of policy-triggered snapshots that are retained for the specified share. When the maximum count is reached, the oldest snapshot is deleted, when the policy creates the next snapshot. You may want to consider the policy schedule and retention for NetBackup's policy protecting Nutanix File shares.
Nested shares do not have Changed File Tracking (CFT) based backup support.
Snapshot operations on nested shares are disabled.
The same file server should not be configured on two separate NSM instances. If such a configuration is done, then there are chances of image import and cleanup failing.