Prepare on-premises Hyper-V servers for disaster recovery to Azure
This article describes how to prepare your on-premises Hyper-V infrastructure for disaster recovery to Azure by using Azure Site Recovery.
This tutorial is the second in a series that shows you how to set up disaster recovery to Azure for on-premises Hyper-V virtual machines (VMs). In the first tutorial, you set up the Azure components that are required for Hyper-V disaster recovery to Azure.
In this tutorial, you learn how to:
- Review Hyper-V requirements.
- Review requirements if your Hyper-V hosts are managed by System Center Virtual Machine Manager.
- Prepare Virtual Machine Manager, if applicable.
- Verify internet access to Azure locations.
- Prepare VMs so that you can access them after failover to Azure.
Note
We design tutorials to show the simplest deployment path for a scenario. The tutorials use default options when possible, and they don't show all possible settings and paths. For more information about a scenario, see the How-to Guides section of the Site Recovery documentation.
Before you start
Make sure that you've prepared Azure as described in the first tutorial in this series.
Review requirements and prerequisites
Make sure Hyper-V hosts and VMs comply with requirements.
- Verify on-premises server requirements.
- Check the requirements for Hyper-V VMs you want to replicate to Azure.
- Check Hyper-V host networking and host and guest storage support for on-premises Hyper-V hosts.
- Check what's supported for Azure networking, storage, and compute after failover.
- Verify that the on-premises VMs you replicate to Azure comply with Azure VM requirements.
Prepare Virtual Machine Manager (optional)
If Hyper-V hosts are managed by System Center Virtual Machine Manager, you need to prepare the on-premises Virtual Machine Manager server.
- Make sure the Virtual Machine Manager server has a least one cloud, with one or more host groups. The Hyper-V host on which VMs are running should be located in the cloud.
- Prepare the Virtual Machine Manager server for network mapping.
Prepare Virtual Machine Manager for network mapping
If you're using Virtual Machine Manager, network mapping maps between on-premises Virtual Machine Manager VM networks and Azure virtual networks. Mapping ensures that Azure VMs are connected to the correct network when they're created after failover.
To prepare Virtual Machine Manager for network mapping:
- Make sure that you have a Virtual Machine Manager logical network that's associated with the cloud in which the Hyper-V hosts are located.
- Ensure that you have a VM network that's linked to the logical network.
- In Virtual Machine Manager, connect the VMs to the VM network.
Verify internet access
For this tutorial, the simplest configuration is for the Hyper-V hosts and the Virtual Machine Manager server to have direct access to the internet without using a proxy.
- Make sure that Hyper-V hosts and the Virtual Machine Manager server, if relevant, can access the required URLs listed in the following table.
- If you're controlling access by IP address, make sure that:
- IP address-based firewall rules can connect to Azure Datacenter IP ranges and the HTTPS port (443).
- Allow IP address ranges for the Azure region of your subscription.
Required URLs
| Name | Commercial URL | Government URL | Description |
|---|---|---|---|
| Microsoft Entra ID | login.microsoftonline.com |
login.microsoftonline.us |
Used for access control and identity management. |
| Backup | *.backup.windowsazure.com |
*.backup.windowsazure.us |
Used for replication data transfer and coordination. |
| Replication | *.hypervrecoverymanager.windowsazure.com |
*.hypervrecoverymanager.windowsazure.us |
Used for replication management operations and coordination. |
| Storage | *.blob.core.windows.net |
*.blob.core.usgovcloudapi.net |
Used for access to the storage account that stores replicated data. |
| Telemetry (optional) | dc.services.visualstudio.com |
dc.services.visualstudio.com |
Used for telemetry. |
| Time synchronization | time.windows.com |
time.nist.gov |
Used to check time synchronization between system and global time in all deployments. |
Prepare to connect to Azure VMs after failover
During a failover scenario, you might want to connect to your replicated on-premises network.
To connect to Windows VMs by using Remote Desktop Protocol (RDP) after failover, allow access as follows:
To access to VMs over the internet, enable RDP on the on-premises VM before failover. Make sure that TCP and UDP rules are added for the Public profile, and that RDP is allowed in Windows Firewall > Allowed Apps for all profiles.
To access to VMs over site-to-site VPN, enable RDP on the on-premises machine. RDP should be allowed in Windows Firewall > Allowed apps and features for Domain and Private networks.
Check that the operating system's SAN policy is set to OnlineAll. Learn more. No Windows updates should be pending on the VM when you initiate failover. If updates are pending, you won't be able to sign in to the VM until the update completes.
On the Windows Azure VM after failover, check Boot diagnostics to view a screenshot of the VM. If you can't connect, check that the VM is running and review these troubleshooting tips.
After failover, you can access Azure VMs by using the same IP address as the replicated on-premises VM, or you can use a different IP address. Learn more about setting up IP addresses for failover.
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for