- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager File System Agent Overview
- Enabling the File System Agent
- About the File System agent
- Application agent and File System agent coexistence
- File System agent prerequisites
- File System agent limitations
- Block-based backups
- Best practices for file system backups
- Configure the file system parallel backup setting
- Configure asset multi-streaming for file-based backups
- Protect an asset with the File System agent
- Protect an asset in a Microsoft Windows Server clustered environment with the File System agent
- Installing and uninstalling the File System agent on AIX
- Installing and updating the File System agent on Linux
- Installing and updating the File System agent on Windows
- Manage the File System agent
- Configure the centralized file-level restore service port number
- Update the application agent in the PowerProtect Data Manager UI
- Moving a File System agent from one PowerProtect Data Manager system to another
- Enable the File System agent after migrating File System assets to a refreshed server
- Managing Storage, Assets, and Protection
- Enable an asset source
- Discover a file system host
- Protection policies for File System agent
- Supported protection policy purposes
- Supported protection policy objectives
- File System replication triggers
- Roadmap for planning a protection policy
- Before you add a protection policy for file system protection
- Add a protection policy for file system protection
- Protection rules
- Cancel a File System agent backup or restore job
- Add a service-level agreement
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Edit the retention period for backup copies
- Delete backup copies
- Host CPU throttling
- Exclusion filters for File Systems
- Centralized restore of a file-system asset
- Updating the File System agent hostname or IP address
- Manage the PowerProtect agent service
- Performing Self-Service Backups and Restores with the File System Agent
- Performing Self-Service Backups and Restores for Disaster Recovery
- Performing Disaster Recovery with the File System Agent in Windows
- Disaster recovery limitations
- Preparing for disaster recovery
- Performing system-state recovery
- Recovering the Active Directory
- Performing bare-metal recovery
- Perform bare-metal recovery of Windows clusters
- Disaster recovery solution for Microsoft SQL application data
- Protecting Microsoft Distributed File System using BMR and SSR
- Performing application restores after bare-metal recovery
- File System Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager 19.14 File System User Guide
File System agent system requirements
Ensure that your environment meets the requirements for a new deployment or update of PowerProtect Data Manager.
Requirements:
NOTE:The most up-to-date software compatibility information for the
PowerProtect Data Manager software and the application agents is provided by the
E-Lab Navigator.
- A list of hosts that write backups to DD systems is available.
- DDOS version 6.1 or later and the
PowerProtect DD Management Center are required. All models of
DD systems are supported.
NOTE:PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version 6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.
- Application agent 19.14 or earlier is required.
- License: A trial license is provided with the PowerProtect Data Manager software. Contact Customer Support for assistance with a permanent PowerProtect Data Manager license.
- Large environments require multiple PowerProtect Data Manager instances. For assistance with sizing requests, contact your Customer Support representative.
- The
PowerProtect Data Manager 19.14 download file requires the following:
- ESXi version 6.5, 6.7, or 7.0.
- 10 vCPUs, 24 GB RAM, one 100 GB disk, and one 500 GB disk.
- The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI.
-
TCP port selected as the
PowerProtect Data Manager communication port from the supported port ranges 7000 to 7009 and 7012 to 7020. The selected port is open between
PowerProtect Data Manager and the application agent host.
NOTE:If a port is not selected from the port ranges, then the default port 7000 is used as the PowerProtect Data Manager communications port.
- VMware ESXi server that hosts
PowerProtect Data Manager meets the following minimum system requirements:
- 10 CPU cores
- 24 GB of RAM for PowerProtect Data Manager
- Five disks with the following capacities:
- Disk 1—100 GB
- Disk 2—500 GB
- Disk 3—10 GB
- Disk 4—10 GB
- Disk 5—5 GB
- One 1-GB NIC
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: <>()\