PowerProtect Data Manager 19.16 File System User Guide

Active Directory Data Recovery at Granular Level

• All or some leaf objects associated to the container may not get restored to original or alternate location in the same host or different host at times. In this case, perform the restore operation for the leaf object again.
• Mounted AD GLR backup copies does not get cleaned up automatically. In this case, manually clean up the temp folder C:\Program Files\DPSAPPS\fsagent\tmp.
• When the number of AD objects are large, the AD GLR mount operation may timeout. In this case, retry the mount operation.
• When mount fails due to an unknown reason, clean up the temp folder manually C:\Program Files\DPSAPPS\fsagent\tmp and retry mount operation.
• Restore operation fails, when restoring the container and the associated AD objects to alternate location. In this case, create a parent object (container object) with the appropriate name similar to the source and then retry the restore operation of only leaf AD objects.

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 Administrator 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.