The following sections provide guidance for troubleshooting backup issues:
After you perform an asset-level restore operation, perform a full backup of the asset to maintain backup consistency.
Unable to move backups to
protection storage
Verify that there is sufficient free space on the
protection storage system.
Unable to discover assets
If the first discovery succeeds and later discoveries fail, verify whether the asset credentials have changed. Update the credentials in
PowerProtect Data Manager accordingly.
Consecutive incremental backups fail
Perform a manual full backup of the NAS asset. The
PowerProtect Data Manager Administration and User Guide provides instructions.
Unable to back up share assets
Verify that the share address and path are valid and mountable. Adding a share does not verify that the share can be backed up.
Unable to back up a NAS appliance because of connectivity errors
You may receive error messages such as
Unable to communicate with NAS appliance when the appliance does not respond as expected and backups may fail to start.
Verify that the NAS appliance is available. Verify connectivity between
PowerProtect Data Manager, the
protection engine, and the NAS appliance. Verify the appliance and management credentials and, if required, update the stored appliance credentials.
For Isilon/PowerScale appliances and protection policies with large numbers of NAS assets, the resulting quantity of REST API calls may exceed the appliance API rate limits. When this happens, the appliance API becomes temporarily unavailable. To work around this limit, move some NAS assets to different protection policies or retry the failed backups.
Unable to back up CIFS shares on PowerScale/Isilon appliances after updating
PowerProtect Data Manager
Perform a manual full backup and then verify that subsequent backups succeed.
Data is not available for the Topic
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: <>()\