- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Network-Attached Storage Overview
- PowerProtect Data Manager 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
- 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
- Protection rules
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Exclusion filters for NAS
- 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 19.14 Network-Attached Storage User Guide
Protection engine limitations
Observe the following points when planning and working with protection engines:
- Deploy protection engines with fully qualified domain names (FQDNs) or IP addresses only. Short names are no longer supported. Existing protection engines which were deployed with short names are deprecated. A future release will require you to delete and redeploy these protection engine with FQDNs or IP addresses instead.
- When you deploy protection engines with FQDNs, each FQDN must have a DNS record.
- Protection engines are part of server disaster recovery backups. However, the disaster-recovery process does not automatically redeploy protection engines.
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: <>()\