Hi, We have a Hub and Spoke topology and have setup the site recovery vaults to replicate between our region A and B. We have enabled 2 private endpoints for our recovery services vault, 1 for each hub and spoke networks/ subnet. When try to setup the replication from region A to B, we are able to setup the replication for the 2 VMs belong to 2 different subnet within Spoke vnet, and they are showing as protected. But for the 2 VMs for Hub vnet (and belongs to 2 different subnets), when try to setup the replication, we are getting this error at "Installing Mobility Service and preparing target" step: Error ID 151195 Error Message Site recovery configuration failed. Possible causes Connection cannot be established to site recovery endpoints due to DNS resolution failure. Recommendation Please make sure that the DNS resolution is working on the virtual machine. Refer to https://aka.ms/asr-dns-issue . Related links https://aka.ms/asr-dns-issue First Seen At We have looked into this Microsoft article and tried to check everything possible but cant get it working. Also as mentioned din this MS article, we are using the default DNS and NOT the custom DNS. Any help would be highly appreciated. Thanks

Site recovery configuration failed - Error ID 151195

Ghulam Abbas 151

Hi,

We have a Hub and Spoke topology and have setup the site recovery vaults to replicate between our region A and B. We have enabled 2 private endpoints for our recovery services vault, 1 for each hub and spoke networks/ subnet. When try to setup the replication from region A to B, we are able to setup the replication for the 2 VMs belong to 2 different subnet within Spoke vnet, and they are showing as protected. But for the 2 VMs for Hub vnet (and belongs to 2 different subnets), when try to setup the replication, we are getting this error at "Installing Mobility Service and preparing target" step:

Error ID 151195
Error Message Site recovery configuration failed.
Possible causes Connection cannot be established to site recovery endpoints due to DNS resolution failure.
Recommendation Please make sure that the DNS resolution is working on the virtual machine. Refer to https://aka.ms/asr-dns-issue.
Related links
- https://aka.ms/asr-dns-issue
First Seen At

We have looked into this Microsoft article and tried to check everything possible but cant get it working.

Also as mentioned din this MS article, we are using the default DNS and NOT the custom DNS.

Any help would be highly appreciated.

Thanks

SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2023-03-20T17:36:58.82+00:00

@Ghulam Abbas Sorry for the inconvenience this must have caused. If you have already tried troubleshooting guidance - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-network-connectivity#issue-1-failed-to-register-azure-virtual-machine-with-site-recovery-151195 then I would suggest you to contact Azure Tech Support team by raising a ticket. 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.
Ghulam Abbas 151 Reputation points

2023-03-21T17:14:42.1533333+00:00

Thanks. Redeployed the private endpoint and retired replication, its now working fine.
SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee

2023-03-21T20:01:40.2833333+00:00

@Ghulam Abbas Thanks for the update. Glad to hear the issue now resolved,