- 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 protection
- 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
- Asset-level configuration for protection policies
- Protection rules
- Cancel a File System agent backup or restore job
- Add a service-level agreement
- Extended retention for protection policies
- Edit the retention period for backup copies
- Delete asset backup copies
- Host CPU throttling
- Enable the use of pre-scripts and post-scripts with backups
- File Filters
- Centralized restore of a file-system asset
- Quick recovery for server DR
- Updating the File System agent hostname or IP address
- Reregister the agent after a PowerProtect Data Manager server hostname or IP address change
- 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
- Deleting temporary files after bare-metal recovery
- Performing Active Directory Data Recovery at a Granular Level
- File System Best Practices and Troubleshooting
- Glossary
PowerProtect Data Manager 19.16 File System User Guide
Changing the preferred host address
You can change the preferred host address that is used for communication between PowerProtect Data Manager and the application-agent host.
The preferred host address can be an IPv4 address , an IPv6 address, or a fully qualified domain name (FQDN).
NOTE:Using an FQDN is only available as of version 19.14 of the application agent.
It is recommended to use an FQDN as the preferred host address in DHCP environments and other environments where static IP addresses can change. When DHCP is used instead of an IP address and the IP address of the host changes, the following benefits occur:
- Communication between PowerProtect Data Manager and the host is uninterrupted.
- Backup and restore operations succeed.
- Reregistration of the application agent is not required.
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: <>()\