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.14 File System User Guide

Centralized file-level restore of a file-system asset

A file-level restore enables the administrator to recover individual files from backups of file systems that were created in PowerProtect Data Manager.

Prerequisites

  • Ensure the following for Linux file-system hosts:
    • You have enabled the SELinux nis_enabled parameter by running one of the following relevant commands:
      • RHEL 8.x or CentOS8.x: setsebool -P nis_enabled 1
      • RHEL 7.x or CentOS7.x: setsebool -P nis_enabled 1
      • RHEL 6.x or CentOS 6.x: setsebool -P allow_ypbind 1

      You can also disable SELinux permanently:

      1. Open the /etc/sysconfig/selinux file in a text editor.
      2. Change the value of SELinux=enforcing from enforcing to disabled.
      3. Restart the host machine.
      4. Verify the SELinux status by running the getenforce command.
    • You have installed the iscsiadm utility by installing one of the following relevant packages on the Linux client:
      • RHEL or CentOS: iscsi-initiator-utils<version_number>.rpm
      • SLES: open-iscsi<version_number>.rpm
    • On SLES, if you want to start the iscsiadm utility for the first time, restart the iSCSI services by running the following command: service open-iscsi restart
    • Review the section Supported platform and OS versions for file system file-level restore for supported platform and operating system versions. PowerProtect Data Manager supports file-level restore only if the backup or replica is on a DD system device.
  • Ensure that you increase the restore request timeout from 10 to 120. This enables you to successfully complete the restoration process for a large number of files. Perform the following steps to increase the restore request timeout.
    1. Log in to the SSH of PowerProtect Data Manager as an admin.
    2. Run the following command to navigate to the /usr/local/brs/lib/adm/config directory.
      cd /usr/local/brs/lib/adm/config
    3. Copy the application.yml file by running the following command.
      cp application.yml application.yml.orig
    4. Open the application.yml file by running the following command.
      vi application.yml
    5. In the application.yml file, change the requestTimeout from 10 to 120.
    6. Save the application.yml file and restart PowerProtect Data Manager.

Steps

  1. From the PowerProtect Data Manager UI, go to Recovery > Assets, and then select the File Systems tab.
    The Restore window displays the file systems that are available for restore. Use View to switch between a list view of all file system assets and a hierarchical view of assets within each File System host that has been discovered in PowerProtect Data Manager.
  2. Select the check box next to the file system, and then click View Copies.
    You can also use the filter in the Name column to search for the name of the specific file system or click the File Search button to search on specific criteria. See File system file-level restore from a search for more information.
    NOTE:The File Search is not supported for Linux files.
    The Restore > Assets window provides a map view in the left pane and copy details in the right pane.

    When a file system is selected in the map view, the file system name appears in the right pane with the copy locations underneath. When you select a specific location in the left pane to view the copies, for example, on a DD system, the copies on that system appear in the right pane.

  3. If the backup is on a DD system, click , and then select from one of the available copies that appear in the table.
  4. In the right pane, select the check box next to the file system backup you want to restore, and then click File Level Restore.
    The File level restore wizard appears.
  5. On the Select target host and mount page, choose from one of the following options, and then click Mount.
    • Restore to Original.
    • Restore to Alternate.
      NOTE:By default, centralized file-level restore operations restore the entire path of selected files and folders to the destination folder. For example, if the file D:\Folder\file1.txt is restored to G:\CFLR, it is restored as G:\CFLR\D\Folder\file1.txt instead of G:\CFLR\file1.txt. However, if you select the Do not retain the upward folder hierarchy while performing recovery option, only the selected file will be restored not the entire folder hierarchy. For example, if the file D:\Folder\file1.txt is restored to G:\CFLR, it is restored as G:\CFLR\file1.txt.
  6. When the mount is complete, click Next.
    The Select folder and files to recover page appears.
  7. On the Select folder and files to recover page:
    1. Expand individual folders to browse the original file system backup, and select the objects that you want to restore to the destination file system.
      You can also use the filter in the Name column to search for the name of the specific object.
    2. Click Next.
      The Select restore location page appears.
    NOTE:When restoring a larger number files without increasing the request timeout, the No files are available for restore. error appears on the Select folder and files to recover page. See the prerequisites of this topic for the procedure to increase the restore request timeout.
  8. On the Select restore location page:
    1. Select the destination drive. Alternatively, choose the Overwrite files in restore location option, in which case existing files on the destination drive will be overwritten.
      NOTE:

      If you choose not to overwrite files and the file or folder has the same name as an existing file or folder, the selected file is renamed either before or after the file extension:

      • On Windows, the selected file or folder is renamed before the file extension. For example, file1.txt is renamed to file1-SSID-timestamp.txt.
      • On Linux, the selected file or folder is renamed after the file extension. For example, file1.txt is renamed to file1.txt-SSID-timestamp.
    2. Browse the folder structure of the destination file system to select the folder where you want to restore the objects.
    3. Click Next.
  9. You can select Troubleshooting mode to enable debug logging, and then select the level of logging to use:
    • Info—Includes information such as status changes. This is the default log level for scheduled backups and restores.
    • Debug—Additional information that helps with problem diagnosis.
    • Trace—The most detailed amount of information for complex problem diagnosis.
    The Summary page appears.
  10. On the Summary page:
    1. Review the information to ensure that the restore details are correct.
    2. Click Finish.
  11. Go to the Jobs window to monitor the restore.
    A restore job appears with a progress bar and start time.

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: <>()\