Azure Site Recovery VCenter connection failed

lufas 26 Reputation points
2021-10-01T12:49:21.647+00:00

Hi there,

im currently facing an issue connection my VCenter using AZSR in the new version 9.45.
Before i updated to the new version everything was working fine and as expected. After the update (which took around 12h, never had this before) the connection to the vcenter failed.
I already checked all recommendations via the error details in the vault, but nothings seems to work. Thus i checked the server and network connections and everything was working as expected. Connection to the process servers is in healthy state. Only the VCenter discovery fails with Error ID 811 (Error Message vCenter is disconnected.) The VCenter is running on 6.7 which is supported and working in other scenarios with Site Recovery aswell.

I started to edit the reg keys for the versioning and managed to install the update for the new rollup agian - problem still exists. Currently no idea how to go into detail with troubleshooting the issue. From my point of view everything should work as expected and there is no more documentation provided to go into detail. Please let me now if you need any logs or something else.

Kind regards

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

Accepted answer
  1. SadiqhAhmed-MSFT 41,296 Reputation points Microsoft Employee
    2021-10-19T07:03:19.507+00:00

    @lufas - Sharing the solution with broader community.

    141644-image.png
    141651-image.png

    ----------------------------------------------------------------------------------------------------------------------

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

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Dennis De Jesus 1 Reputation point
    2022-03-29T20:29:59.713+00:00

    We don't have any other configuration servers. Is there any other solution we can try? We are having the same problem since we upgraded to version 9.48.0.0

    0 comments No comments