This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(153.6, 83%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
After export/import several VMs from 2012r2 to 2022 and upgrading the configuration the Site Recovery is not recognising the new location of the VMs to continue with the replication to Azure. The new server is associated to the same hyper-v site as the previous server and it recognises there are VMs available to back up
@Bright_Admin Thank you for contacting us!
We need more details to assist you further.
Did you in-place upgrade the Hosts or moved the VMs from one Host to another?
Moved from one host to another
Are those machines part of the cluster and registered to ASR, only then it would work else just moving to new hosts doesn't work.
As they are separate os versions 2012r2 and 2022 they are not able to be put in to a cluster. So will the ASR job need to be deleted and recreated?
Apologies for delayed response.
Yes, your understanding is correct. The OS versions of all the servers within the cluster needs to be the same. For now, you need to start from scratch to set up ASR. Doc ref: https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-support-matrix#on-premises-servers