locked
Deploy Site Recovery for client with existing Azure VNet and Production VMs RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    A client has already extended their network into Azure via a Site-to-Site VPN and has deployed a number of domain joined VMs that are all working well in their production environment.

    They now want to deploy Azure Site Recovery to provide a DR solution for other on-premises Hyper-V VMs and I understand the basic requirements but was wondering if we can replicate them to the existing VNet (with production VMs) or if we have to use a new VNet?

    The main reason I ask is that they already have a Domain Controller VM in the Production VNet that would save them having to replicate one from on-premises.

    Cheers for now

    Russell 

    Wednesday, October 4, 2017 3:31 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can replicate them to your existing Vnet but replicated VMs will have to be configured with new IP (Vnet) when you want to activate them.

    Also, if you want to place replicated VMs in different Vnet, you need to configure VPN connectivity with new Vnet.

    Please go through below link

    https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-support-matrix-to-azure

    • Marked as answer by RSBurnell Monday, October 9, 2017 3:43 PM
    Monday, October 9, 2017 8:33 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can replicate them to your existing Vnet but replicated VMs will have to be configured with new IP (Vnet) when you want to activate them.

    Also, if you want to place replicated VMs in different Vnet, you need to configure VPN connectivity with new Vnet.

    Please go through below link

    https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-support-matrix-to-azure

    • Marked as answer by RSBurnell Monday, October 9, 2017 3:43 PM
    Monday, October 9, 2017 8:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the confirmation Manoj.

    Presumably, you could use VNet peering rather than a VPN to connect the different VNets (assuming they're in the same Region of course)?

    Cheers for now

    Russell

    Monday, October 9, 2017 3:43 PM