PowerProtect Data Manager 19.9 Network Attached Storage User Guide

Backup

• NAS shares do not display a value for backup size until after the first backup completes.
• When you remove or delete a discovered asset from an appliance, the next discovery cycle marks that asset as not detected. Backups of that asset fail while the asset is marked as not detected.

Restricted access shares

For NAS appliances, the NAS agent successfully backs up discovered shares with the No Access property. The appliance permits a snapshot of the share despite access restrictions, and the agent backs up the snapshot.

To prevent backups of restricted-access shares, add the share as an exclusion. For CIFS and NFS shares, the agent honors the permission and the backups fails. All restore operations for restricted asset shares fail for both appliances and shares.

Restore and FLR

• NAS backups do not support FLR from backups on remote (replicated) protection storage or from backups in a cloud stage (Cloud Tier).
• When you search with FLR for folders, the folder size may be incorrectly shown as zero even when the folder contains files and other folders of nonzero size. Restore operations are unaffected.
• Selecting 500 or more files or folders in a single FLR operation may return an error message or encounter browser limitations. To work around the limitation, restore the next higher folder or split large FLR operations into multiple smaller operations. FLR operations to restore folders that contain more than 500 files or subfolders are unaffected.
• For FLR, selecting both a file or folder and its parent folder from the same backup may result in inconsistent renaming of duplicate restored data. Select files and folders that do not share a parent/child relationship and select only the parent folder to recover everything in that folder. For example, instead of selecting /foo and /foo/bar, select only /foo.
• Unity and PowerStore appliances have known mounting issues with NFS v3 and v4. Share-level recovery and FLR fail with an error when you restore to the original or alternate location under the following conditions:
  • NFS v3: The NFS export path contains the file system name followed by a forward slash (/). For example, 10.2.3.4:/filesystem_name/share_name.
  • NFS v4: The NFS export path contains a forward slash (/). For example, 10.2.3.4:/test/share.
  NOTE The NFS syntax imposes one forward slash immediately after the colon (:) as part of the separation between host and path (host:/path). Instead, this limitation applies to any additional forward slashes that are present in the path (filesystem_name/share_name).
  Instead, restore to a location where these conditions are not present.

• When you perform FLR on different versions of a file from multiple backups of a Linux file server, unexpected behavior may occur. If you select the options to restore to the same folder and overwrite original files, PowerProtect Data Manager does not mark the restored files with the transaction ID. Instead, the restore operation appends the complete path to the expected restore location.

  For example, the file /mnt/tmp/backup/dir4/test.txt that should be restored to /mnt/tmp/backup/mnt/tmp/backup/dir4/test_transactionid.txt is instead restored to /mnt/tmp/backup/mnt/tmp/backup/mnt/tmp/backup/dir4/test.txt. Other share types are not affected.

  Perform separate FLR operations to restore files and folders from one backup at a time.

• For FLR and share-level restore, to restore from a backup of an asset which is no longer part of a protection policy, set asset-level credentials.
• You can only cancel FLR operations at the job level. PowerProtect Data Manager does not support FLR cancellation for individual assets.
• You cannot restart NAS FLR jobs.
• For FLR, exporting the logs at the asset level may produce unexpected results. To work around the limitation, export the logs at the job level.
• For FLR, when you select Restore and Overwrite the Original Files and Folders, the operation restores the selected files and folders to the root level of the destination. The operation leaves the original files and folders untouched. If files and folders with the same name exist at the destination, the restore operation renames the recovered files and folders.
• When restoring NFS shares to alternate locations, the UI prompts you for credentials even though NFS shares do not require credentials. However, the restore fails unless you provide the same credentials that were used to create the protection policy.
• Asset counts are missing on the Jobs page for restore operations.
• For Isilon/PowerScale appliances:
  • When you perform an asset-level restore to the NAS over NFS, PowerProtect Data Manager restores the backup contents to a new base folder whose name reflects the destination asset name.
  • When you perform an asset-level restore to the NAS over CIFS, PowerProtect Data Manager restores the backup contents to a new base folder whose name reflects the source asset name.

Access control lists (ACLs)

• If you restore a backup to a share that uses a different protocol version from the original share, then the ACLs of the restored files and folders may not exactly match the originals.
• If a share is offered through multiple protocols, the backup preserves only the ACLs for the selected protocol, not for any others.
• When PowerProtect Data Manager cannot preserve the ACLs during a backup, that backup completes with an exception.

Server disaster recovery

• For PowerProtect Data Manager 19.9, NAS protection functionality is not a part of PowerProtect Data Manager server disaster recovery.
• Quick Recovery is not supported for NAS.

Backup stream counts

During a NAS backup, the reported active stream count may not be correct until the backup completes or until all active streams from a NAS protection engine close. During this time, the reported active stream count may not match the number of active streams as reported by PowerProtect DD. Most often, this issue occurs during full backups with large slice sizes.

Appliance protection

For Isilon/PowerScale appliances, the PowerProtect Data Manager asset list may show two additional discovered entries: /ifs/.snapshot and /ifs. These entries are process artifacts, not valid assets, and you can ignore them. Do not add these assets to a protection policy other than an exclusion policy.