- 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
Install the File System agent on Linux in silent mode
On Linux, review the following commands to perform a silent installation of the File System agent.
NOTE:The
--server option is used to specify the
PowerProtect Data Manager server IP for registration, and is mandatory for silent install.
To verify the authenticity and integrity of the RPM files prior to the installation step, follow the instructions in the PowerProtect Data Manager Security Configuration Guide.
Use the following commands to perform a silent installation on Linux:
- For silent installation, including registration of the agent with the PowerProtect Data Manager server, type: install.sh --silent-install --server=<PowerProtect_Data_Manager_server_IP>
- To run the installer in debug mode during silent installation, type: install.sh --debug --silent-install --server=<PowerProtect_Data_Manager_server_IP>
- To skip installation of the block-based backup driver, type: install.sh --skip-driver --silent-install --server=<PowerProtect_Data_Manager_server_IP>.
-
To specify the FQDN, IPv4 address, or IPv6 address of the File system agent host to be registered, and the port to be used for communication between the agent and
PowerProtect Data Manager, type:
install.sh --silent-install --server=<PowerProtect_Data_Manager_server_IP> --preferred-address=<agent_host_FQDN_or_IP> --client-port=<port_number>
NOTE:The port number must be from the supported port ranges 7000 to 7009 and 7012 to 7020. If you do not specify a port number, the default port 7000 is used as the communication port. The ports 7010 and 7011 are used by the agent service message bus.
- To enable the PowerProtect Data Manager communication TCP port, run the /opt/dpsapps/agentsvc/configfw.sh script as the root user.
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: <>()\