Migrating to Azure using Azure Site Recovery (ASR), Read this first
Azure Site Recovery has evolved a lot since it was launch in late 2014, and have continuously added features. Microsoft is investing lot of money and effort to capture the Migration and most Importantly Disaster Recovery as a Service (DRaaS) market. In this article, I will cover some of the important factors that you must consider with their possible remediation plans.
Azure Site Recovery (ASR) for Azure Resource Manager (ARM or V2) is now in Public preview and supports Azure Backup for Virtual Machines, Replication and Site Recovery.
Points to Remember (for Physical Server Migrations) –
- Windows Server Disks should be Basic
- Standard Azure Limitations Apply
- Drive Letter E is reserved in Azure. So, if you have source server with Data in E Drive that needs to be migrated then the driver letter needs to be changed
- Shared Disks are not supported
- Failover Clusters are not supported
- The Servers should be running 64-bit Operating Systems of Windows 2008+
- Hostnames, Mount Points, Device Names and Windows System Paths should be in English language
- Operating System should be installed on a C Drive
- iSCSI and FC Disks are not supported
- Requires Admin Access on Source Machines for Agent Deployments
- UEFI and EFI isn’t supported
- ASR Supports Standard Storage and not Premium Storage at this point
For VMware or Hyper-V workloads there are seperate limitation in addition to above and I will cover them in Part-2.
The article will also be updated with mitigation plans.