Review the following prerequisites before installing and using the
File System agent in
PowerProtect Data Manager.
Windows, Linux, and AIX prerequisites
Ensure that your host is a 64-bit system.
PowerProtect Data Manager supports only 64-bit hosts.
Ensure that your host is a supported operating system version. Software compatibility information for the
PowerProtect Data Manager software is provided in the
E-Lab Navigator.
Ensure that all clocks on both the host and
PowerProtect Data Manager are time-synced to the local NTP server to ensure discovery of the backups.
Ensure that the host and the
PowerProtect Data Manager network can see and resolve each other. If
PowerProtect Data Manager and the
File System agent are registered in different domains, you must add IP address and Fully Qualified Domain Name (FQDN) entries on both the client and server.
Browse to the path of the hosts file. For example, on Windows
C:\Windows\System32\drivers\etc\hosts, and on Linux
/etc/hosts.
Add an entry to the hosts file, as in the following:
IP address FQDN common name
10.10.100.100 yourdomain.com yourdomain
LVM and VxVM partitions or volumes are supported.
Physical partitions are supported only when using file-based backups.
Each volume group on LVM2 or VxVM must have at least 10% free space for a block-based backup to succeed. For successful Windows VSS snapshot during block-based or file-based backup, the free space requirement is 20%.
For file-based backups, ensure that the drive on which the File System agent is installed has adequate free space for the metadata record files that are created during a backup. Provide about 250 MB free space for each million files that you are backing up.
For any ESXi version 6.5 or earlier host with PowerStore storage attached, the Windows operating system deployment or installation cannot proceed. If the
DiskMaxIOSize parameter is not configured with the proper value, the
File System agent backup and restore operations fail. Ensure that you set the
DiskMaxIOSize to 1024 KB.
Ensure that no service is using port 7010 or 7011. These ports must be reserved for File System agent operations.
File system discovery requires an ext3, ext4, XFS, or BTRFS file system type.
On the Linux hosts that have the UEFI Secure Boot option enabled, block-based backup drivers do not load, and the error message
insmod: ERROR: could not insert module /lib/ modules/ 3.10.0-693.el7.x86_64/ extra/nsrbbb.ko: Required key not available appears. As a workaround, you can disable the Secure Boot option.
Ensure that the file system has the
/etc/fstab entry. Without the
/etc/fstab entry, discovery fails.
To enable file-level restores, complete the following:
Log in to the system you are restoring from as
root.
Install iSCSI client packages.
See the Operating System documentation for the installation procedure.
For
Service Start, choose
Manually, and then click
OK.
If installing the block-based backup driver, review the output of the
cat /proc/sys/kernel/kptr_restrict file to verify that permissions to install the driver are set. If the value is set to
2, then there is a restriction that might result in block-based backup driver installation failure. Run the following command to change this setting:
echo 1 > /proc/sys/kernel/kptr_restrict
Install the lsb_release package.
See the Operating System documentation for the installation procedure.
Additional AIX prerequisites
File system discovery requires a JFS or JFS2 file system type.
Ensure that IBM XL C or C++ Runtime for AIX 16.1.0.7 and later is installed.
Data is not available for the Topic
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: <>()\