The ASR support for VMware to Hyper-V protection/migration scenario is under roadmap for a while now. Enterprise customers and hosting partners are requesting this scenario since Microsoft acquired InMage. Like in the VMware-to-Azure scenario, a near zero downtime protection/migration can be achieved using the same InMage Scout technology.
Customers and partners are requesting a Microsoft owned solution for VMware to Hyper-V migration and ASR is the perfect solution for this.574 votes
Please leverage partner tools for this scenario
Currently Extended replication is unsupported for Azure site recovery. Site recovery should fully support all features of server 2012 R2 hypervisors including extended replication.396 votes
Create one ore more Dev-Test environments by failing over the replicated VMs and let them always run. Unlike a Test Failover, ASR would never cleanup this environment40 votes
Please refer to this link https://azure.microsoft.com/en-us/services/devtest-lab/
When trying to install the ASR agent on a 2012r2 physical server with UEFI boot, we get an error stating that UEFI boot physical servers are not supported.32 votes
This is a duplicate item
I protect VMs using my production subscriptions, and when I initiate a planned / unplanned event, the VM spins up in such subscription.
When I want to initiate a test failover, I want those resources to spin up in resources (Storage / vnet) on a separate subscription dedicated to dev/test.28 votes
We only support test failover and planned failover in same subscription. DR drill ensures preparedness for the actual disaster
Microsoft, please enble GRS to LRS feature in Recovery vault after perform Azure VMs or File & folder backups.
It is much needed feature for our clients21 votes
To be raised with Azure Backup service
I use two op-premises Hyper-V host on two site without VMM.
Like between an op-premise Hyper site and Azure,
I want to recovery between two on-premises Hyper-V host.20 votes
Use Hyper-V replica for achieving the same
I want to know "Failover" button's mean eiter failover from on-premises Hyper-V Site to Azure, or failback from Azure to on-premises Hyper-V Site.
Now, same word "Failover" is used for failover and failback in Buttons / Job messages.2 votes
Failback is always with a direction. Failover from A to B and Failover from Bt o A – where failover from B to A is failback.
i can not connect to my service http://trumedicines.cloudapp.net/tablets1 vote
If you are having issues in protection or failover, kindly file a support issue or you can use the forum to get a quick help.
This is already allowed for all the Vm – Enterprise to Enterprise as well as Enterprise to Azure. Once you protect – you need to ensure that the VM does not have a spaces in the name since Azure does not allow that.
- Don't see your idea?