PowerProtect Data Manager 19.14 Storage Array User Guide

/storage-hosts API timeout error when restoring using Instant Access

When performing an Instant Access restore, if you select either Map to Host or Map to Host Group on the Location page of the Block Volumes Restore wizard, a timeout error may occur. This might happen if there is a network connectivity issue between PowerStore and PowerProtect Data Manager. The issue can also occur if the PowerStore REST API is delayed in fetching the host details and sending a response back to the /storage-hosts API.

If this error occurs, the following message is displayed:

As a workaround, close the error message dialog and retry the operation.

Unable to update the remote system after changing the storage unit password

If you try to change the password of an existing storage unit in PowerProtect Data Manager while a backup is in progress, the backup job fails along with the array configuration job that is triggered by the storage unit password change.

The array configuration job fails with the following error even though the remote system is not in use by any protection jobs:

org.springframework.web.client.HttpClientErrorException$BadRequest:
400 Bad Request: "{"messages": [{"code":"0xE02010020086","severity":"Error","message_l10n":"Failed
to modify the remote system protection_policy1-ldpde105-b9ab3 due to associated active remote
sessions.","arguments":["protection_policy1-ldpde105-b9ab3"]}]}"

To resolve this issue, contact Customer Support.

Instant Access fails for backup and restore sessions that are in an In-Progress, Canceling, or Failed Cleanup Required state

Instant Access fails for backup and restore sessions that are shown as In-Progress, Canceling, or Failed Cleanup Required in PowerStore Manager.

To resolve this issue for Instant Access jobs that are shown as In-Progress or Canceling, wait until the job completes and then retry the Instant Access operation in the PowerProtect Data Manager UI.

To resolve this issue for Instant Access jobs that are shown as Failed Cleanup Required in PowerStore Manager and Failed in PowerProtect Data Manager, complete the following steps in the PowerProtect Data Manager UI:

1. Click in the Details column next to the job.

   PowerProtect Data Manager displays the error details and the steps to resolve the issue.

2. Complete the steps to resolve the issue, and then retry the Instant Access operation.

If an Instant Access job fails with the error message clean up in progress in PowerStore Manager, wait until the operation completes. Once the operation is complete, retry the Instant Access operation in the PowerProtect Data Manager UI.

Volume groups that do not contain any volumes cannot be protected and are not discovered as part of the initial discovery of the asset source in the PowerProtect Data Manager UI.

If a volume group was added to a protection policy when it was not empty, but is now empty and a subsequent discovery is performed, the volume group is still shown in the list of assets in the PowerProtect Data Manager UI. Backups that are performed while the volume group is empty will fail with an error.

Empty volume groups can be kept when there were backups taken before the volume group was empty that might need to be restored. To restore data that was backed up before the volume group was empty, use Restore to alternate and select a different volume group as the target.

Protection operations fail intermittently when encryption in-flight is enabled from PowerStore

Enabling encryption in-flight on the remote system from PowerStore causes backups and restores to fail intermittently.

To resolve this issue, wait until the remote system returns to an OK state, and then retry the backup or restore operation.

Unable to restore from replicated backups using Instant Access

Instant Access restores from replicated backup copies fail with the following error:

org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request: "{"messages":[{"code":"0xE0204001002F","severity":"Error","message_l10n":"Instant Access/Retrieve operation failed because remote snapshot 89d298f5-ae7e-485b-934c-63e27b35d6c2 does not belong to the remote system 96c0782a-d228-4bb4-9bfb-1698a10e3d37.","arguments":["89d298f5-ae7e-485b-934c-63e27b35d6c2","96c0782a-d228-4bb4-9bfb-1698a10e3d37"]}]}"

Protection policy configuration fails due to an invalid X.509 certificate verification code

During protection policy configuration, if the array configuration job fails with the error Unable to import the certificate. Verification code : 3, the CA certificate cannot be imported due to an invalid certificate verification code. As a result, the protection policy configuration cannot complete successfully.

If the CA certificate was generated on a PowerProtect DD system with DD OS version 7.5 or earlier, the certificate does not contain the CA:TRUE extension. PowerStore rejects any CA certificate that lacks the CA:TRUE extension.

To resolve this issue, regenerate the self-signed CA certificate:

1. On the DD system, open a command prompt and type the following command:

   adminaccess certificate generate self-signed-cert regenerate-ca

   Regenerating the certificate breaks existing trust relationships with peer systems.

2. To restore the trust relationship, add the new DD certificate to the truststore of the peer system.

Protection and restore operations fail after replacing DD protection storage system

After performing either a DD migration or DD head swap, backup and restore operations fail.

To resolve this issue, perform the following steps from the PowerProtect Data Manager UI:

1. From the left navigation pane, select Protection > Protection Policies.
2. Select the protection policy that has the migrated DD configured, and click Edit.
3. Next to the primary backup, click Replicate, and then click Add.

   Do not change the storage unit information for the primary backup objective.

4. In the Add Replication dialog, select the same DD storage system that is being used for the primary backup and new storage unit, and then click Save.
5. On the Protection Policies page, select the protection policy, and click Protect Now.
6. On the Configuration page, select Replicate Now, and then select All copies.
7. Click Next.
8. On the Summary page, review the settings and then click Protect Now. After the operation completes, backups that were created on the original storage unit before the DD migration appear under the Replicate objective on the Restore > Assets > View Copies page.
   NOTE:

   • You can restore the copies to either the original location or to an alternate location.
   • You cannot restore these copies using Instant Access.
9. On the Protection Policies page, click Edit.
10. On the Objectives page, under Primary Backup, click Edit.
11. In the Edit Primary Backup dialog, select the new storage unit, and then click Save.

    If replication is not required for newer backups, remove the replication objective from the policy.