Configure failover of multiple IP addresses with Azure Site Recovery
Every NIC attached to a VM has one or more IP configurations associated to it. Each configuration is assigned one static or dynamic private IP address. Each configuration may also have one public IP address resource associated to it. A public IP address resource has either a dynamic or static public IP address assigned to it. To learn more about IP addresses in Azure, read the IP addresses in Azure article.
Today, Site Recovery automatically configures the failover of the Primary IP Configuration. This article describes how you can configure failover of Secondary IP Configs with Site Recovery. Please note that this is supported only for Azure VMs.
Configure Secondary IP Address Failover via Azure portal
Site Recovery automatically configures the failover of your Primary IP Configuration when you Enable Replication for the VM. Secondary IP Configurations need to be manually configured after the Enable Replication completes. For this you need a protected VM that has one or more Secondary IP Configurations.
Follow these steps:
Navigate to the Network blade on the Replicated Items page.
You will see the following highlighted text. Click on Edit to modify it.
Click on "+ IP Configurations". You will see two options, Either add all IP Configurations, or selectively add IP Configurations.
On clicking Add all secondary IP Configurations, all of them will appear in the grid below, and then you can configure them as you like.
Alternatively, on clicking Select and add secondary IP Configurations, a blade will open where you can pick and add IP Configurations you'd like to configure for failover.
Now, for each IP Configuration that you've added, you can configure the values for Private IP, Public IP, and Backend Pool for Failover and Test Failover separately. After you've done it all, don't forget to Save changes.
Next steps
- Learn more about Traffic Manager with Azure Site Recovery
- Learn more about Traffic Manager routing methods.
- Learn more about recovery plans to automate application failover.
Feedback
https://aka.ms/ContentUserFeedback.
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:Submit and view feedback for