- 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
Configure PowerProtect Data Manager for NAS protection
Prepare the PowerProtect Data Manager server by performing the following initial system configuration tasks:
About this task
The PowerProtect Data Manager Administrator Guide provides more information about each task. If your environment already protects other assets, you may have already completed some of these tasks.
Steps
- Add protection storage.
- (Optional) Configure a storage unit.
- Configure virtual networks, if applicable.
-
Configure the
PowerProtect
Search Engine, if needed.
The Search Engine is required for File Level Restore (FLR).
- Enable the virtual machine asset source and register the vCenter server where you intend to deploy the protection engine.
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: <>()\