Forum Discussion
Azure Site Recovery : On-Prem to Azure vis Site-to-Site VPN
Hi,
I have Site-to-Site VPN betweem Azure & On-Prem. In Azure, I have one Resource Group in which I have one VNET 10.0.0.0/8.This VNET is further divided into four subnets out of which one subnet is used for Azure site recovery in which replicated VM will resides & get IP from this subnet during failover.
I have Windows 2012 R2 DC without VMM & my guest OS is Windows 7 which is running on it.
My Site-to-Site VPN is working fine. I have configured Azure site recovery & I see Hyper-V host is green under Hyper-V site in ASR. But when I go to my on-prem server, I see guest-os VM is in crtical state & 0% synchronize. I use the storage account in Azure & I allow all the subnets just in case but still its in critical state.
I delete the site-recovery-valult in Azure & remove/uninstalled any ASR related service/software from my on-prem server. I created new site-recovery-vault with different name & now I trying to add again the same server. I downloaded the Azure Site Recovery Installer & new Vault key on my on-prem server but get enclosed error:
I have went through all Microsoft blogs for ASR & done everything right from GUI to CLI script with multiple reboots of server but no luck.
Earlier I was one step behind & now I am two step behind.
I will be glad if someone from Microsoft team can guide step-by-step here (for my scenario only. I have read Microsoft ASR doc but no luck).
I am in free trial mode now so cant open ticket but will go paid if solution works in lab environment.
Regards
Vinod Singh
Hi
This is due to the registry key that stays in the registered server. to remove it follow following link
Thanks
Hello,
Has your problem been solved? I do not have any problem with ASR, but I noticed in the documentation that Microsoft say that it is incompatible with site-to-site VPN. It works only with ExpressRoute.
Now that is odd. I don't understand why - even if the target respository (Vault) is a blob storage with a public endpoint - so what - why should a s2s vpn not be able to be used?I'd love to know if your s2s vpn works or not with this.
