Azure Site Recovery Error ID 310060

CHEZDATECH 1 Reputation point

Hello, has anyone experienced this error and know how to clear it. Replication is working and we see no issues but the replication health shows as critical. We had a successful test fail over on July 30th so this error with an inaccurate date is causing the error to appear in the health and status page.


thank you

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
677 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 40,986 Reputation points Microsoft Employee

    Hi @CHEZDATECH Thank you for your patience and I apologize for the inconvenience caused!

    I see, you mentioned that Azure Site Recovery notifications are triggered for health in critical state. However, replication seems to be happening as is. Usually, these alerts are triggered when there is communication failure. For example: If port 443 is disabled or network connectivity is blocked.

    Can you ensure that you upgraded the process server agent to 9.48. Ideally upgrades do not cause any failures. But at times, a network blip may cause these kinds of issues.

    Good thing is, the replication is not affected, and you receive successful heartbeats from process server and vCenter.

    I don't find this to be a problem. But if this is causing any replication failure then that need to be investigated further to understand root cause for this issue.

    Could not think of anything other than a restart of ASR services might work. If you are interested in investigating this issue further, you can contact Azure site recovery 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 - to create support case.

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

    0 comments No comments