This blogpost will shortly describes the steps what I did when I did the ASR between my on-premises (VMM/Hyper-V) and the Microsoft Azure from DNS settings point of view. Reason why I did the following changes was that I want to update DNS records automatically and fast after the failover.
I´m currently rebuilding my demo environment and I already have S2S VPN up and running between my datacenter and Microsoft Azure. Next thing what I´m planning to install is Azure Site Recovery (with VMM). I wanted to create own VNET for the DR purposes in Azure so I´m going to configure VNET peering between ASR VNET and the VNET which has the VPN connection to the on-premises. This blog show the simple steps how I did that.
This blogpost continues configuration of ASR Enhanced VMWare to Azure protection. First blogpost can be found from HERE. In this second post I´m going configure Prosess Server to Azure (which is needed for failback to on-premises) and also show failover to Azure and Failback to on-premises.
As I´m big fan of ASR I definitely wanted to test ASR Enhanced version of VMware to Azure. I will show you the steps which you need to do to get it up and running.
This post include also vCenter configuration steps.
Just a short reminder of some possibilities what you can do with ASR:
Migration (for example migrate VMs to Azure)
Disaster Recovery (DR to Azure or another datacenter)
Dev/test (for example test production env on Azure with isolated network)
We had some problems during the installation and I want to share them to you.
Hope these cases help you troubleshoot issues if have any.
In this blogpost we will create Recovery Plan and test failover. Note that in SAN replication all virtual machines associated with a replication group must fail over together. This is because failover occurs at the storage layer first.
This blog post contain following steps
create new VM under ASR SAN Replica protection
move existing vm under ASR SAN Replica protection
We have been working on ASR SAN replication for a while and it has been very interesting journey and therefore I wanted to share my steps what we did and how. We were using NetApp products for this case.
We have been testing different ASR solutions and we had problems to manage SAN replication with the following error message “error, there are no storage arrays on the source”. This blogpost gives you needed information how you can solve this.