PowerProtect Data Manager 19.14 Storage Direct User Guide

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:

1. Open the Storage Direct configuration file in an editor.
2. 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.
3. Remove the parent storage group in the configuration file.
4. 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:

1. Run the following restore prepare command with the scan parameter:

   protectpoint restore prepare scan backup-id <backup_ID> config-file <file_path>

2. Run either one of the following restore release commands with the scan parameter:

   protectpoint restore release scan backup-id <backup_ID> config-file <file_path>

   protectpoint rollback backup-id <backup_ID> scan config-file <file_path>

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>

Updated primary PowerProtect Data Domain user password is not replicated to the secondary PowerProtect Data Domain

After updating the primary PowerProtect Data Domain user password, it is not replicated to the secondary PowerProtect Data Domain user. Perform the following to verify whether the secondary PowerProtect Data Domain user password is updated:

1. Navigate to C:\Program Files\DPSAPPS\ppfsagent\bin. The DPSAPPS folder is created by the appagent during the installation.
2. Run the following command:

   protectpoint config validate dd-system primary/secondary config-file <path of config file>

   For example:

   protectpoint config validate dd-system primary config-file "C:\Program Files\DPSAPPS\ppfsagent\config\233G_4.config"
   		  

   If the secondary PowerProtect Data Domain user password is not updated, the system throws this error: "Unable to connect to DD Boost index database: 'Unable to connect to '<DD ip>' because user '<user name>' does not have sufficient access rights or a valid credential. Please check and try again!'. Error code: 15022.

   To update the secondary PowerProtect Data Domain user password, perform the following:

   1. Go to the respective secondary PowerProtect Data Domain and check for the user name for which the password needs to be updated. You can also check the user name from the above error.
   2. Run the following command:

      mtree list

   3. Update the same password that updated in UI for the primary PowerProtect Data Domain user using the following command:

      user change password <user name>

   4. Verify whether the secondary PowerProtect Data Domain user password is updated in the config file.