You might encounter the following issues while performing backups.
Creation of new snapshot after restart of failed backup
Storage Direct agent creates a new snapshot when restarting failed backup jobs in
PowerProtect Data Manager.
If a backup fails and you restart the backup job, the Storage Direct agent creates a new snapshot and does not reuse the snapshot that was created during the failed backup. This is expected behavior, and the latest snapshot is used for the new backup.
Troubleshooting a configuration file that is generated by
PowerProtect Data Manager and imported during an agent update
If a Storage Direct configuration file generated by one
PowerProtect Data Manager system is imported as an existing Storage Direct configuration file into a second
PowerProtect Data Manager system, the parent storage group is not created during asset configuration in the existing VMAX storage group protection policy.
Before you add the configuration file to the
appsetting file, complete the following steps:
Open the Storage Direct configuration file in an editor.
Set the
VMAX_FASTX_RESTORE_SG parameter to the restore storage group that is created by
PowerProtect Data Manager.
NOTE: If there are multiple storage groups, enclose each entry in a comment. Ensure that you follow the config file format. See
Configuration file requirements for more information.
Remove the parent storage group in the configuration file.
Delete the parent storage group from the VMAX storage array by running the
symcli command.
Storage policy backup failure and PowerProtect config validation error
If the password of a
DD Boost/vdisk user contains a backslash (\) or a forward slash (/) or a quotation mark (") or any combination of these three characters during the storage policy configuration for a new Storage Direct environment, the policy backup and
PowerProtect config validation fail. This issue occurs in both self-service and centralized backup processes.
When the policy backup fails, the user interface displays an error as shown below:
Some tasks failed during the operation.Please consult the individual task status for more information.
A sample
PowerProtect config validation error:
[root@XXXXX ~]# protectpoint config validate config-file /opt/dpsapps/ppfsagent/config/149_5_new.config
*** Using VMAX configuration file "/opt/dpsapps/ppfsagent/config/149_5_new.config" ***
Validating the application settings.....................[OK]
Note: APP_INFO has not been specified. No value will be used, which is acceptable.
Validating the host requirements........................[OK]
Validating the Primary system:
DD vdisk connection information.....................[Error]
**** Unable to connect to DD system '<DD system IP address>' as user '149_5-XXXXX-6b648': Invalid user specified..
Note: DDBoost communication method is Network
DD Boost connection information.....................[Error]
As a workaround, from the
PowerProtect Data Manager user interface, reset the password of the
DD Boost/vdisk user without a backslash (\) or a forward slash (/) or a quotation mark (").
Troubleshooting method to retrieve a backup catalog deleted using the force option with retention lock enabled
When you use the force option to delete the backup with retention lock enabled on the static image, the static image will not be deleted but the backup entry from the catalog will be removed. As the result, the backup will not be listed and cannot be restored, though the static image for the backup is available on the
DD system. Perform the following steps to retrieve such a backup catalog:
Run the following restore prepare command with the scan parameter:
The scan catalog is created with the backup deleted using the force option with retention lock enabled. Run the following command to check the restored backup entry in the catalog:
protectpoint backup show list scan config-file
<file_path>
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: <>()\