PowerProtect Data Manager 19.11 File System User Guide

Restores

You might encounter the following issues while performing restores with the File System agent.

Centralized file-level restore operations

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 to G:\CFLR\D\Folder\file1.txt instead of G:\CFLR\file1.txt.

Add -g to the file-level restore command to restore only the file. See Self-service file-level restore of file systems for more information.

File-level restores of symbolic-linked directories

The file-level restore of a symbolic-linked directory does not contain any symbolic links or reparse points, but the contents are the same as the source directory.

Create symbolic links manually after the file-level restore operation completes.

File-level restore operations fail with a client services error

When performing a file-level restore, you might see an error similar to one of the following:

Resource not found. Check if client services are running and perform the operation again.

ARA0002: Unable to restore FILE_SYSTEM asset F:\ because of an agent issue.

The restore was unsuccessful because of an agent issue.

The File System restore was unsuccessful because a Status code 500 error occurred during the request to the Agent host.

Perform the operation again.

File sparseness and Linux file-level restores

Linux file-level restores of file-level backups do not retain file sparseness.

Use the appropriate tools to reduce disk space.

Restores of clustered drives fail with an agent host timed out error or a network connectivity error

When attempting to restore a clustered drive, you might see an error similar to one of the following:

The File System restore was unsuccessful because the request to the Agent host timed out.

ARA0005: Unable to restore FILE_SYSTEM asset C:\ClusterStorage\Volume3 because of a network connectivity issue on agent host w2019c2.agent.com.

The restore was unsuccessful because of an issue with the network connection.

To resolve this issue: 1.Check the network connectivity between PowerProtect Data Manager and the agent host. 2.Confirm that there is no packet loss between PowerProtect Data Manager and the agent host.

Perform a full discovery of the logical cluster host, and then retry the restore. For more information about performing a full discovery, see the PowerProtect Data Manager Administration and User Guide.

Restoring block-based backups on 16 TB ReFS volumes

Image-level restore operations of File System agent block-based backups (BBB) might fail ReFS volumes with 16 TB or higher capacity.

Restore the data by using file-level restore (FLR).

Restoring multiple backups or SSIDs from the command-line interface

A single-level restore command-line interface (CLI) cannot be used to select multiple backups or SSIDs for restore.

Open a separate file-level restore CLI for each backup or SSID.

XFS restores of block-based backups

When performing an XFS restore of a block-based backup on a remote host, the kernel version of the remote host must be equal to or higher than the kernel version of the source host.

There is no workaround.