Re-protect error

Question

Re-protect error

Tyler Saville 431

Hello, I am getting this error when trying to reverse replicate (re-protect) from azure site recovery. Anyone know anything I can check? Many thanks.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-18T14:10:46.75+00:00

@Tyler Saville Sorry for the inconvenience this must have caused you!

Error 531505 in Azure Site Recovery (ASR) occurs when the replication appliance is unable to access the initial replication or resynchronization logs from the cache storage account. This can happen due to a variety of reasons, such as network connectivity issues, incorrect credentials, or insufficient permissions.

To resolve this issue, you can try the following steps:

Check the network connectivity between the replication appliance and the cache storage account. Ensure that the replication appliance has access to the cache storage account over the required ports and protocols.

Verify that the credentials used to access the cache storage account are correct. Ensure that the account has the necessary permissions to access the storage account.

Check the replication policy settings to ensure that the correct cache storage account is selected. If the cache storage account is incorrect, update the replication policy to use the correct account.

Check the replication logs to identify any errors or warnings that may be preventing the replication appliance from accessing the cache storage account. You can find the logs in the following location: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\logs.

If none of the above steps resolve the issue, try deleting and recreating the replication policy. This will create a new cache storage account and may resolve any issues with the existing account.

If you continue to experience issues, you can create a support request for further assistance!
Tyler Saville 431 Reputation points

2023-10-19T14:24:54.8533333+00:00

Thanks for the info, I will try to duplicate this in my lab and delete/recreate the replication policy to see if that fixes it.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-19T14:46:43.1666667+00:00

@Tyler Saville Let us know how it goes!
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-23T07:00:33.84+00:00

@Tyler Saville Did you get a chance to try the suggested steps in your LAB?
Tyler Saville 431 Reputation points

2023-10-23T11:59:41.0233333+00:00

I have not yet, hoping to be able to start this week, just been super busy.
Tyler Saville 431 Reputation points

2023-10-30T17:47:49.94+00:00

I have this setup in my lab now. I failed over and deleted then recreated the replication policy but still getting errors that the replication appliance cannot access the cache storage account. Is the cache storage account different from the storage account? Any ideas? Thank you
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-01T10:21:17.7133333+00:00

@Tyler Saville Yes, the cache storage account is different from the storage account.

ou need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. Cache storage accounts must be Standard.

Using a cache ensures minimal impact on production applications that are running on a VM.

Learn more about cache storage requirements.

To change default cache storage account, select Advanced settings. Refer to - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-quickstart#enable-replication-for-the-azure-vm
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-02T14:35:18.2133333+00:00

@Tyler Saville Does that answer your question?
Tyler Saville 431 Reputation points

2023-11-02T17:50:15.0466667+00:00

I am still facing issues. I can ping my storage account IP from the modernized site recovery appliance on-prem. The logs at E:\rcmprotectagent\logs are saying the request was terminated bc the entity is being throttled.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-02T18:24:38.3766667+00:00

@Tyler Saville Can you ensure that the bandwidth is set per recommendations? - https://learn.microsoft.com/en-us/troubleshoot/azure/site-recovery/manage-protection-network-bandwidth-usage
Tyler Saville 431 Reputation points

2023-11-02T19:36:25.6+00:00

I have reviewed this, but the issue remains
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-03T12:14:09.5433333+00:00

@Tyler Saville I recommend you contact Azure technical support team by raising a support request. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

FYI: https://azure.microsoft.com/en-us/support/plans/
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-08T08:15:37.3966667+00:00

@Tyler Saville Did you get a chance to reach out to Azure technical support team?
Tyler Saville 431 Reputation points

2023-11-08T16:31:49.4433333+00:00

Hi, yes we have opened a case with them
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-09T14:27:05.7966667+00:00

@Tyler Saville Let us know if there is any update from support professional.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-13T06:24:58.45+00:00

@Tyler Saville Any progress on the support request?
Tyler Saville 431 Reputation points

2023-11-13T18:33:17.09+00:00

Not very much movement yet, my engineer that was working with them is on vacation this week. I'll post any updates though, thanks for checking back.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-20T06:30:47.38+00:00

@Tyler Saville Any goods news yet?
Tyler Saville 431 Reputation points

2023-11-20T15:04:09.6866667+00:00

Still working with them, they have collected a lot of logs so far
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-28T07:24:15.99+00:00

@Tyler Saville Did you hear back from support?
Tyler Saville 431 Reputation points

2023-11-28T13:05:56.83+00:00

They have setup a lab to try to duplicate the issue on their end
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-05T13:51:22.6566667+00:00

@Tyler Saville Any update from support team?
Tyler Saville 431 Reputation points

2023-12-05T13:55:38.2133333+00:00

Hello, we are still working with them, it has just been very slow going. They don't work with us daily so we just have to wait. I will be sure to post back here with any resolutions though, thank you.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-05T14:25:35.28+00:00

@Tyler Saville Thanks for the update. Looking forward to hearing a good news from you! :)
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-11T08:41:08.92+00:00

@Tyler Saville Did you hear back from support?
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-14T10:02:28.7+00:00

@Tyler Saville Haven't heard back yet!
Tyler Saville 431 Reputation points

2023-12-14T12:44:49.75+00:00

Microsoft product group was able to apply a hot fix. They said it will be included in version 9.57 whenever it is released.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-14T13:22:07.9066667+00:00

@Tyler Saville Thanks for the update! Glad to hear it is resolved through hot fix deployment.

Do you have a support request # for this issue? If yes, please share it with us. Thanks!
Tyler Saville 431 Reputation points

2023-12-18T16:00:07.37+00:00

It should be this one, Case 2311130030004658
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-20T09:33:56.9+00:00

@Tyler Saville Thanks for sharing the support request #.

Answer accepted by question author

0 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-18T14:10:46.75+00:00

@Tyler Saville Sorry for the inconvenience this must have caused you!

Error 531505 in Azure Site Recovery (ASR) occurs when the replication appliance is unable to access the initial replication or resynchronization logs from the cache storage account. This can happen due to a variety of reasons, such as network connectivity issues, incorrect credentials, or insufficient permissions.

To resolve this issue, you can try the following steps:

Check the network connectivity between the replication appliance and the cache storage account. Ensure that the replication appliance has access to the cache storage account over the required ports and protocols.

Verify that the credentials used to access the cache storage account are correct. Ensure that the account has the necessary permissions to access the storage account.

Check the replication policy settings to ensure that the correct cache storage account is selected. If the cache storage account is incorrect, update the replication policy to use the correct account.

Check the replication logs to identify any errors or warnings that may be preventing the replication appliance from accessing the cache storage account. You can find the logs in the following location: C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\logs.

If none of the above steps resolve the issue, try deleting and recreating the replication policy. This will create a new cache storage account and may resolve any issues with the existing account.

If you continue to experience issues, you can create a support request for further assistance!
Tyler Saville 431 Reputation points

2023-10-19T14:24:54.8533333+00:00

Thanks for the info, I will try to duplicate this in my lab and delete/recreate the replication policy to see if that fixes it.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-19T14:46:43.1666667+00:00

@Tyler Saville Let us know how it goes!
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-10-23T07:00:33.84+00:00

@Tyler Saville Did you get a chance to try the suggested steps in your LAB?
Tyler Saville 431 Reputation points

2023-10-23T11:59:41.0233333+00:00

I have not yet, hoping to be able to start this week, just been super busy.
Tyler Saville 431 Reputation points

2023-10-30T17:47:49.94+00:00

I have this setup in my lab now. I failed over and deleted then recreated the replication policy but still getting errors that the replication appliance cannot access the cache storage account. Is the cache storage account different from the storage account? Any ideas? Thank you
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-01T10:21:17.7133333+00:00

@Tyler Saville Yes, the cache storage account is different from the storage account.

ou need a cache storage account in the source network. During replication, VM changes are stored in the cache before being sent to target storage. Cache storage accounts must be Standard.

Using a cache ensures minimal impact on production applications that are running on a VM.

Learn more about cache storage requirements.

To change default cache storage account, select Advanced settings. Refer to - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-quickstart#enable-replication-for-the-azure-vm
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-02T14:35:18.2133333+00:00

@Tyler Saville Does that answer your question?
Tyler Saville 431 Reputation points

2023-11-02T17:50:15.0466667+00:00

I am still facing issues. I can ping my storage account IP from the modernized site recovery appliance on-prem. The logs at E:\rcmprotectagent\logs are saying the request was terminated bc the entity is being throttled.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-02T18:24:38.3766667+00:00

@Tyler Saville Can you ensure that the bandwidth is set per recommendations? - https://learn.microsoft.com/en-us/troubleshoot/azure/site-recovery/manage-protection-network-bandwidth-usage
Tyler Saville 431 Reputation points

2023-11-02T19:36:25.6+00:00

I have reviewed this, but the issue remains
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-03T12:14:09.5433333+00:00

@Tyler Saville I recommend you contact Azure technical support team by raising a support request. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

FYI: https://azure.microsoft.com/en-us/support/plans/
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-08T08:15:37.3966667+00:00

@Tyler Saville Did you get a chance to reach out to Azure technical support team?
Tyler Saville 431 Reputation points

2023-11-08T16:31:49.4433333+00:00

Hi, yes we have opened a case with them
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-09T14:27:05.7966667+00:00

@Tyler Saville Let us know if there is any update from support professional.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-13T06:24:58.45+00:00

@Tyler Saville Any progress on the support request?
Tyler Saville 431 Reputation points

2023-11-13T18:33:17.09+00:00

Not very much movement yet, my engineer that was working with them is on vacation this week. I'll post any updates though, thanks for checking back.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-20T06:30:47.38+00:00

@Tyler Saville Any goods news yet?
Tyler Saville 431 Reputation points

2023-11-20T15:04:09.6866667+00:00

Still working with them, they have collected a lot of logs so far
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-11-28T07:24:15.99+00:00

@Tyler Saville Did you hear back from support?
Tyler Saville 431 Reputation points

2023-11-28T13:05:56.83+00:00

They have setup a lab to try to duplicate the issue on their end
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-05T13:51:22.6566667+00:00

@Tyler Saville Any update from support team?
Tyler Saville 431 Reputation points

2023-12-05T13:55:38.2133333+00:00

Hello, we are still working with them, it has just been very slow going. They don't work with us daily so we just have to wait. I will be sure to post back here with any resolutions though, thank you.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-05T14:25:35.28+00:00

@Tyler Saville Thanks for the update. Looking forward to hearing a good news from you! :)
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-11T08:41:08.92+00:00

@Tyler Saville Did you hear back from support?
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-14T10:02:28.7+00:00

@Tyler Saville Haven't heard back yet!
Tyler Saville 431 Reputation points

2023-12-14T12:44:49.75+00:00

Microsoft product group was able to apply a hot fix. They said it will be included in version 9.57 whenever it is released.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-14T13:22:07.9066667+00:00

@Tyler Saville Thanks for the update! Glad to hear it is resolved through hot fix deployment.

Do you have a support request # for this issue? If yes, please share it with us. Thanks!
Tyler Saville 431 Reputation points

2023-12-18T16:00:07.37+00:00

It should be this one, Case 2311130030004658
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-12-20T09:33:56.9+00:00

@Tyler Saville Thanks for sharing the support request #.

Answer 1

@Tyler Saville Much appreciate your patience throughout the support tenure on Microsoft Q&A platform and with Azure technical support team.

"Sharing the summary of the issue for benefit of broader community"

Issue: 0% synchronized during re-protect to alternate location.

Cause: Product Group identified bug in the code. The root cause of the bug is the data protection process hanging when an exception/failure occurs. Our Product Group will improve the behavior to ensure it exits gracefully without breaking re-protection or implement improvements on what should occur in the code if the problem surfaces.

Resolution:
Hot fix will be deployed to all customers during release of version 9.57. If auto-update is not enabled, connect to the appliance and launch configuration manager from the desktop to install the latest components if needed.

If the response helped, do "Accept Answer" and up-vote it

Share via

Re-protect error

0 additional answers

Your answer