Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
679 questions
Azure Site Recovery Reprotect VM fails error ID 110050. Old Vcenter server to blame? How do I delete it?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 33%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Donald MacPherson
0
Reputation points
Hi,
I'm testing our ASR instance and ran into an issue. Failover of VM from VMware to Azure works fine but when I click the Reprotect button, I receive this error:
"maxwell" was the hostname of a previous vcenter server, now decommissioned. I don't know why it would show in the error message as the replication job was created using the new host and so was the re-protect job (the current host is the only one available in the dropdown menu).
The old host still appears in the replication appliance, but I see no option to remove it, only edit it. Editing to blank fields doesn't work, just makes them marked red for mandatory.
I also see no way to remove it from the Azure admin portal.
Appreciate any advice
{count} votes
-
SadiqhAhmed-MSFT 41,381 Reputation points Microsoft Employee2024-07-15T13:08:28.56+00:00 @Donald MacPherson Thank you for contacting us through Microsoft Q&A platform. Happy to help!
It seems that you are facing an issue while re-protecting a VM from VMware to Azure. The error message you received indicates that the replication job was created using the old vCenter server hostname "maxwell" which is now decommissioned.
To resolve this issue, you can try the following steps:
Remove the old vCenter server from the replication appliance. To do this, you can edit the replication appliance settings and remove the old vCenter server from the list of vCenter servers. If you are unable to remove it, you can try to add a new vCenter server and then remove the old one.
Once you have removed the old vCenter server from the replication appliance, you can try to re-protect the VM again. Make sure that you select the correct vCenter server hostname while creating the replication job.
If you are still unable to re-protect the VM, you can try to remove the replication job and create a new one. To remove the replication job, go to the Azure portal, select the replication job, and click on the "Delete" button. Once you have removed the replication job, you can create a new one and select the correct vCenter server hostname.
Hope this helps. Let us know if you need further assistance in this matter.
If the response helped, do "Accept Answer" and up-vote it
Sign in to comment