Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
697 questions
Failover test switching to Prod network
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 24%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Lori
0
Reputation points
I am having an issue in that during failover, the machines are not switching to the test failover network; instead, they are connecting to the production network. This happens also when a new failover network is created and tested also. Any suggestions?
{count} votes
-
SadiqhAhmed-MSFT 44,336 Reputation points Microsoft Employee2024-08-22T20:26:12.1933333+00:00 @Lori Sorry for the delayed response!
It sounds like you're facing a challenging issue with your failover process. Please follow the instructions below:
- Ensure that the test failover network is properly configured and isolated from the production network. The test network should mimic your production network, including the same number of subnets, subnet names, and IP address ranges.
- Verify that the NSGs are correctly configured for the test failover network. Missing or incorrectly configured NSGs can prevent the machines from connecting to the test network. Make sure that the required rules are in place and that the NSGs are associated with the correct network interfaces.
- Check the DNS and DHCP settings for the test failover network. Ensure that the DNS is updated with the IP address specified for the DNS VM in the Compute and Network settings. If you're using DHCP, make sure it is set up correctly for the test failover.
- When performing a test failover, make sure to select the correct test failover network in the Compute and Network settings for each VM. By default, the test failover should use an isolated network.
- Review the test failover logs and diagnostics to identify any errors or issues that might be causing the machines to connect to the production network instead of the test network.
If these steps do not resolve the issue, you might need to consult with your network administrator or Microsoft Azure technical support for further assistance.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
Let us know how it goes!
If the response helped, do "Accept Answer" and up-vote it
Sign in to comment
Sign in to answer