Troubleshooting storage array backup and restore issues
The following sections provide guidance for troubleshooting backup and restore issues.
Configuration job started due to change in protection storage IP address fails
When you change a protection storage system's IP address in
PowerProtect Data Manager, the configuration job that is triggered by the protection storage discovery fails to update the remote system on the PowerStore array.
If this issue occurs, run the configuration job again.
Timeout error with /storage-hosts API 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:
504: Gateway timeout error
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.
Unable to complete data protection operations when a remote PowerStore system goes into "PARTIAL DATA CONNECTION LOSS" state
Backup, restore, and instant access operations for block volume protection policies cannot complete successfully when a remote PowerStore system goes into
PARTIAL DATA CONNECTION LOSS state and does not instantly return to
OK state.
This issue occurs primarily due to network connectivity disruptions, and can usually be resolved by maintaining a stable network. The PowerStore system typically returns to
OK state without intervention. If the network is stable but the network error under the
Connectivity tab of the remote system persists, and the remote system does not return to
OK state within 10 to 15 minutes, contact Dell 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:
Click
in the
Details column next to the job.
PowerProtect Data Manager displays the error details and the steps to resolve the issue.
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.
When backups were performed before the volume group was empty, the empty volume groups can be retained if the backups might require a restore. 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 for the completion of the configuration job that was started when the option was enabled, and until the remote system returns to an
OK state, and then retry the backup or restore operation.
NOTE:For remote systems that are created in
PowerProtect Data Manager, changing the settings of the remote systems from PowerStore is not recommended.
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"]}]}"
Block volume Restore to Original might fail with error
A Restore to Original of a block volume might fail with the following error:
org.springframework.web.client.HttpClientErrorException$BadRequest: 400 Bad Request... Retrieve session already exists for a given resource
To resolve this issue, contact Dell Customer Support.
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
DDOS 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:
On the
DD system, open a command prompt and type the following command:
Regenerating the certificate breaks existing trust relationships with peer systems.
To restore the trust relationship, add the new
DD certificate to the truststore of the peer system.
Internal Server error due to target protection storage user password or user account issue
During a storage array configuration, backup, or restore job, the following error might occur on the PowerStore system when the target protection storage user password is incorrect or the target protection storage user account has been locked or disabled:
org.springframework.web.client.HttpServerErrorException$InternalServerError:
500 Internal Server Error: "{"messages":
[{"code":"0xE02010020082","severity":"Error","message_l10n":"Operation on
remote system failed due to internal error, try again. If the error persists,
contact your service provider for assistance."}]}"
If the cause of the error is an incorrect password, change the password using the following steps:
Change the target protection storage user password in the
PowerProtect Data Manager UI.
Change the same password in the corresponding credential object.
Retry the job.
If the job continues to fail with the same error, the account might be disabled. Contact Dell Customer support for more information about the steps required to enable the account again.
Re-create a
PowerProtect Data Manager user with the role
user that has been accidentally deleted
A new target protection storage user is created as part of the configuration job for PowerStore block volume protection policies. The password for this user is managed by
PowerProtect Data Manager, and the name of this user is in the format
user_ targetStorageName_UniqueIdentifier. If this user is accidentally deleted, then you can re-create this user with the same username credentials. In the
PowerProtect Data Manager UI, go to
Administration > Credentials to obtain the username.
If the target protection storage is a
DDsystem or
DDVE system, log in to the
DDOS to create a user with the role
user.
After re-creating the user, ensure that you change the password in the corresponding credentials object, and maintain the same password in the
PowerProtect Data Manager UI. Go to
Administration > Credentials, select the user, and click
Edit to update the password.
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: <>()\