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 Network-Attached Storage User Guide

Snapshot troubleshooting

The following sections provide guidance for troubleshooting snapshot issues:

Unable to create a snapshot

On the NAS appliance, verify whether the backup operation would exceed any of the snapshot limits. System-wide and directory snapshot limits vary by appliance. The appliance documentation provides more information.

If necessary, remove any snapshots that are no longer required and then try the backup again. Verify that the NAS appliance management credentials are correct. Check the NAS appliance licensing.

Unable to create a snapshot on PowerScale

Confirm that you have shared the required paths for CIFS and NFS protection. NAS appliance protection prerequisites provides more information.

Unable to mount an appliance snapshot or share asset

Download the NAS protection workflow logs. Review protection logs provides instructions.

Open snapshotAndSlice.log and copy the mount command from the log. Replace the password placeholder with the appliance or share credential. Use the appliance or file server console to test the mount command.

Use the output from the mount command on the appliance or file server console to troubleshoot. Resolve configuration issues such as invalid credentials or connectivity problems. If there are no configuration issues, contact Customer Support.

PowerScale backup times increase

An increasing number of snapshots in /ifs/.snapshot may reduce appliance performance, resulting in increased backup times. Creating snapshots for assets under the same path can also reduce appliance performance. Some task failures may also result in failure to delete a snapshot. Remove unneeded snapshots to restore performance. Manually delete PowerScale snapshots provides instructions.

Backup cancellation or failure prevents snapshot deletion on PowerScale

If you cancel backups for multiple assets, circumstances may prevent removal of the corresponding snapshots from the appliance. If the backup status is Failed, retrieve and examine the log bundle. Where a system report, job status, or log indicates that the snapshot was not deleted, manually remove the snapshot. Manually delete PowerScale snapshots provides instructions. The log bundle for the backup contains the ID for the corresponding snapshot.

Unable to identify stale snapshots on the appliances

Perform the following steps to identify the stale snapshots that are created through PowerProtect Data Manager for NAS and delete such stale snapshots:

  • In PowerProtect Data Manager UI, on the Jobs > Protection Jobs page, identify the backup jobs that failed and use the following methods to identify the stale snapshots in such jobs.
    • Export the logs and identify the failed backup jobs. In the NAS Agent Logs, the snapshotDetails attribute provides the snapshot details.
    • If any NAS Protection backup job fails during the first step (Performing crawl and slicing of NAS Asset) of the backup operation, stale snapshots can exist in the appliance.
    • If any NAS Protection job is completed with the Completed With Exceptions status and if the summary of exceptions under job details indicates the following error, There was failure while deleting snapshot, stale snapshots can exist in the appliance.
  • See the specific appliance documentation for the steps to delete stale snapshots directly from the appliance.
NOTE:Stale snapshots are generated only for completed jobs. Hence, do not delete any snapshots that are created with a protection job with the In Progress status else the backup operation may fail.

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