Quick post to clarify some frequently asked questions on the newly announced
Azure Site Recovery
service which enables you to protect your Hyper-V VMs to Microsoft Azure. The FAQ will
address every feature capability - it should help you get started.
Q1: Did you just change the name from Hyper-V Recovery Manager to Azure Site Recovery?
A: Nope – we did more than that. Yes, we rebranded Hyper-V Recovery Manager to
Azure Site Recovery
(ASR) but we also brought in a bunch of new features. This includes the much awaited capability to replicate virtual machines (VMs) to Microsoft Azure. With this feature, ASR now orchestrates replication and recovery between private cloud to private cloud as well as private cloud to Azure.
A: In Jan 2014, we announced the general availability of Hyper-V Recovery Manager (HRM) which enabled you to manage, orchestrate protection & recovery workflows of *your* private clouds. You (as a customer) owned both the primary and secondary datacenter which was managed by SCVMM. Built on top of Windows Server 2012/R2 Hyper-V Replica, we offered a
cloud integrated Disaster Recovery Solution
Q3: HRM was an Azure service but data was replicated between my datacenters? And this continues to work?
A: Yes on both counts. The service was being used to provide the “at-scale” protection & recovery of VMs.
Q4: What is in preview as of June 2014 (now)?
A: The rebranded service now has an added capability to protect VMs to Azure (=> Azure is your secondary datacenter). If your primary machine/server/VM is down due to a planned/unplanned event, you can recover the replicated VM in Azure. You can also bring back (or failback) your VM to your private cloud once it’s recovered from a disaster.
Q5: Wow, so I don’t need a secondary datacenter?
A: Exactly. You don’t need to invest and maintain a secondary DC. You can reap the benefits of Azure’s SLAs by protecting your VMs on Azure. The replica VM does *NOT* run in Azure till you initiate a failover.
Q6: Where is my data stored?
A: Your data is stored in *your* storage account on top of world class geo-redundant storage provided by Azure.
Q7: Do you encrypt my replica data?
A: Yes. You can also optionally encrypt the data. You own & manage the encryption key. Microsoft never requires them till you opt to failover the VM in Azure.
Azure is a rapidly evolving platform and these restrictions are applicable as of June 2014.
Q15: Any gotchas with network configuration or memory assigned to the VM?
A: Just like the previous question, when you failover your VM, you will be bound by Azure’s offerings/features of IaaS VMs. As of today, Azure supports one network adapter and upto 112GB (in the A9 VM). The product does not put a hard-block in case you have a different network and/or memory configuration on-premises. You can change the parameters with which a VM can be created in the Azure portal under the Recovery Services option.
Q16: Where can I find information about the product, pricing etc?