Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.12 File System User Guide

Install the File System agent on Linux in interactive mode

Use this interactive procedure to Install the File System agent on supported Linux systems.

Prerequisites

NOTE If a value is not provided for PowerProtect Server IP in the installation commands, the product is installed without PowerProtect registration, and no backups can be initiated from the UI.

Steps

  1. In the PowerProtect Data Manager UI:
    1. Click Settings icon, and then select Downloads from the System Settings menu.
    2. Select the File System agent download package for Linux, fsagent1912_linux_x86_64.tar.gz.
    3. Download the package in the location that you want to install the File System agent.
      NOTE Relocating the installation to another partition or mount point on Linux is not supported.
  2. Untar the installer by running tar -xvf fsagent1912_linux_x86_64.tar.gz.

    Then, run the command cd fsagent to change the current working directory to the extracted path.

    NOTE 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.
  3. Run the installation script install.sh.
    To run in debug mode, run install.sh --debug.
    To get help, run install.sh --help.
    NOTE For installations on Oracle Linux distributions or CentOS Linux distributions (for CentOS 8.0, 8.1, and 8.2), run install.sh --skip-driver to skip the block-based backup driver installation. These distributions do not currently support block-based backups. All backups performed by the File System agent on these distributions will be file-based backups.

    For RHEL distributions (for Red Hat 8.0, 8.1, and 8.2), Security-Enhanced Linux (SELinux) is enabled by default. It can support block-based backups, provided you continue the installation with the procedure in Install the File System agent on RHEL distributions.

    The following .rpm or .deb files are installed as part of the script:
    • powerprotect-agentsvc.rpm or powerprotect-agentsvc.deb—Installs or updates the agent service component for the File System agent.
    • ppdm_bbbwt.rpm or ppdm-bbbwt.deb—Installs the block-based backups driver.
    • ppdm_fsagent.rpm or ppdm-fsagent.deb—Installs the File System agent related files and folders.
  4. Type the PowerProtect Data Manager server FQDN or IP address. It is recommended to use the FQDN.
    NOTE
    • If another application agent is already installed on the client and registered to PowerProtect, ensure that you register the agent with the existing PowerProtect Data Manager server FQDN. When you register the agent with a PowerProtect Data Manager server that is different from the currently registered server, no warning message appears, and requests are routed to the newer server instance.
    • If you specify a hostname or fully qualified domain name (FQDN) with an underscore (_) for the PowerProtect Data Manager server, then the communication will be done by the system's IP, if provided the system on registration.
  5. To enable the PowerProtect Data Manager communication 7000 TCP port, run the /opt/dpsapps/agentsvc/configfw.sh script as the root user.
    The system responds that the firewall script is running, and is configuring firewall rules.
    NOTE If the firewall rules are not applied, restart the firewall.

Next steps

If the host is not already approved, add the file system host to the PowerProtect Data Manager server. Manage the File System agent provides more information.

Discover file system assets. Discover a file system host provides more information.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  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: <>()\