PowerProtect Data Manager 19.16 File System User Guide

Backing up Windows ACL properties

On a Windows client, if the contents of a file have not changed since the last backup but the Access Control List (ACL) properties have, incremental backups will not back up the changed ACL properties.

Perform the following steps to back up the changed ACL information:

1. Enable Last Access from the client by running the command fsutil behavior set disablelastaccess 0.
2. Restart the client.
3. Check the status by running fsutil behavior query disablelastaccess and looking for DisableLastAccess = 0 in the output.
4. Set the detect-acl-changes flag to true. The value of this flag is false by default. Edit the C:\Program Files\DPSFSAGENT\settings\.ddfssv.fsagentconfig file and change "--detect-acl-changes=true" to set the flag.

Take note of the following:

• When the --detect-acl-changes flag is set, the file is treated as a modified file and is backed up as part of the next backup.
• If ACL modifications are made only to executable files residing on a mounted volume, the changes might not be backed up.
• This works only for files, not folders. Changes only to the ACL properties of folders cannot be backed up.

Backups fail when credentials include a backslash character (\)

When you enter credentials that include a backslash character (\) for an application agent in the PowerProtect Data Manager UI, the backups fail.

For example, when you enter a password for the operating system or database user that includes the backslash character, subsequent backups fail with the following error message:

This error might occur when updating the password for a storage unit.

To resolve this issue, type \\ (double backslash) instead of \ (single backslash) when you enter the credentials for an application agent in the PowerProtect Data Manager user interface.

Backup pre-script or post-script fails on Linux when the Run As option specifies a non-privileged user

When you use a pre-script or post-script with a backup and specify non-privileged user credentials for the Run As option, the agent service runs the script as the non-privileged user. On Linux, when you specify the non-privileged user credentials for the Run As option in the PowerProtect Data Manager UI, the corresponding script fails during the backup operation.

In the PowerProtect Data Manager UI, the script job is listed as failed with the following error:

Password: su: Authentication failure

The backup job status is listed as either Success or Completed with Exceptions.

As a workaround, set the script file permissions to 755 in the repos/scripts directories, and then rerun the backup with the required scripts.

Block-based backup driver installation

The following message might appear during the installation of the block-based backup driver: Block based backup driver was installed but not loaded. If the driver cannot be loaded, file-based backups will be performed instead of block-based backups.

Perform the following troubleshooting steps in order. Unless otherwise noted, if you make a change at any step, test block-based backups again before proceeding to the next step:

1. If the bc utility is not installed, install the utility.
2. If the livepatch module is installed and enabled, disable it.
3. Install or reinstall the block-based driver ppdm-bbbwt.
4. Restart the nsrbbb service. For information on the specific commands to execute, refer to the documentation of the host's operating system.

Linux block-based incremental backups fail

On Linux, the block-based incremental backups consistently fail and display a message similar to save: Block Based Error subsystem error while performing Block Based Backup.

Check if any other process is already accessing the snapshot or delete the snapshot manually, and then try again.

Block-based backup fail with meta_bg attribute

PowerProtect Data Manager notice [WTFSWarn] Unable to fetch used blocks from FSParser. Error 0

Workaround:

Switch to file-based backup, volumes with meta_bg can be protected using File based backup.

Edit Retention button is disabled for asset copies

On the Infrastructure > Assets page > Asset <asset name> page, the Edit Retention button is disabled.

The Edit Retention button is enabled only when the copy status of the asset source is Available. In detail, if deleting a copy of a protected asset fails, the Copy Status will be updated to another state from Available, and the Edit Retention button is disabled.

Workarounds are:

• Edit the retention period of an asset copy if its status is Available.
• Do not try deleting an asset copy before its retention period.