- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Network-Attached Storage Overview
- PowerProtect Data Manager Appliance overview
- Additional procedures for system administrators
- NAS appliance protection prerequisites
- NAS protection limitations
- Resolved limitations
- NAS protection deployment recommendations
- Encryption in-flight
- Roadmap for NAS protection
- Multiple VLAN support for NAS
- Supported Internet Protocol versions
- Security configuration
- Slicer library for high-density file system
- Support for NFS 4.1 and 4.2
- Managing Assets and Protection
- About NAS protection
- Enable the NAS asset source
- Add a NAS appliance
- Add a NAS share
- Assets configuration support for DNAS
- Edit or delete a NAS asset source
- Discovering and adding PowerScale configured with SmartConnect and multiple access zones
- Deploy a protection engine for NAS asset protection
- Add a centralized protection policy for NAS assets
- Cancel a NAS protection job
- Protection rules
- Extended retention for protection policies
- File Filters
- Restore a NAS asset to the original location
- Restore a NAS asset to an alternate location
- NAS file level restore using File Search
- Restore PowerScale top-level path and permissions
- Protection engine parameters
- Determine protection engine usage for a protection job
- Change the protection engine Docker network range
- Network-Attached Storage Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager Appliance 5.16.0.0 Network-Attached Storage User Guide
Support for NFS 4.1 and 4.2
PowerProtect Data Manager Appliance supports NFS versions 4.1 and 4.2.
Dell arrays
The NAS agents checks for the NFS version number, if the NFS version is 3, then the agent mounts the share with NFSv3 only.
If the version is NFSv4 , then the agent mounts the share without any protocol version that is defined in mount command. The proxy host (NAS client) and NAS Server negotiates the version that can be used to mount and access the share. Once the share is mounted, then agent retrieves the version from the mount string from /proc/mount, and returns this version to NASDM.
Generic NAS
The NASDM receives only CIFS or NFS share but does not receive any version information.
The agent mounts the share without any protocol version that is defined in mount command. The proxy host (NAS client) and NAS Server negotiates the version that can be used to mount and access the share. Once the share is mounted, then agent retrieves the version from the mount string from /proc/mount, and returns this version to NASDM. If the mount fails, the agent goes to NFS v3 and mounts the share.
NOTE:For NFSv3 , only attributes are read along with file data by FSA. For NFSv4 , the ACLs, extended attributes, and attributes are read along with file data by FSA.
NOTE: The mount activity proceeds with the highest supported version.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\