Recovery Services Failover, no network and agent not ready

%3CLINGO-SUB%20id%3D%22lingo-sub-2282542%22%20slang%3D%22en-US%22%3ERecovery%20Services%20Failover%2C%20no%20network%20and%20agent%20not%20ready%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282542%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20using%20Recovery%20Services%20to%20protect%20a%20bunch%20of%20our%20on-prem%20servers%20that%20are%20on%20ESXI%206.7.%20We%20are%20having%20issues%20with%20a%20few%20of%20our%20older%20machines%20which%20are%202008R2%2C%20while%20we%20are%20working%20to%20get%20rid%20of%20these%20with%20our%20vendor%20we%20have%20found%20when%20we%20do%20our%20Test%20Failovers%20to%20Azure%2C%20we%20cannot%20get%20the%20Network%20to%20work%20or%20the%20Agent%20to%20go%20into%20a%20Ready%20status.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20machines%20are%20running%20Azure%20VM%20Agent%20ver%202.7.41491.949.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESometimes%20when%20I%20toggle%20the%20%22Test%20Connection%22%20under%20Connect%20-%20RDP%20it%20seems%20to%20jog%20the%20system%20and%20get%20it%20going%2C%20but%20it's%20not%20consistent.%26nbsp%3B%20I%20have%20also%20tried%20switching%20from%20DHCP%20to%20Static%20and%20back%2C%20changing%20subnets%2C%20doing%20the%20redeploy%20option%20and%20these%20seem%20to%20never%20get%20it%20going.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20machines%20have%20every%20update%20in%20Windows%20update%20on%20them%2C%20the%20firewalls%20are%20disabled%20as%20we%20handle%20that%20at%20the%20network%20level%20here%2C%20there%20is%20no%20software%20that%20would%20block%20this.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20or%20things%20that%20might%20help%20with%20the%20failover%20establishing%20connection%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2283134%22%20slang%3D%22en-US%22%3ERe%3A%20Recovery%20Services%20Failover%2C%20no%20network%20and%20agent%20not%20ready%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2283134%22%20slang%3D%22en-US%22%3EWill%20do%2C%20thanks%20so%20much%20I%20will%20try%20these%20now%20and%20start%20testing%20monday%20morning%201st%20thing.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20so%20much!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282976%22%20slang%3D%22en-US%22%3ERe%3A%20Recovery%20Services%20Failover%2C%20no%20network%20and%20agent%20not%20ready%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282976%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20suggest%2C%20following%20fixes%20might%20help%20to%20consistent%20network%20%26amp%3B%20RDP.%3C%2FP%3E%3CP%3E1)%20Disable%20NLA%20(%20Azure%20portal-%20VM%20-%26gt%3B%20Operations%20-%26gt%3B%20Run%20command%20-%26gt%3B%20Execute%20Disable%20NLA%3CBR%20%2F%3E2)%20Ensure%20the%20VM%20Network%20effective%20route%20has%20advertised%20the%20On-Prem%20%26amp%3B%20Azure%20network%20gateway%3CBR%20%2F%3E3)%20Ensure%20any%20persistent%20route%20gateway.%20If%20any%20obsolete%20gateway%20update%20to%200.0.0.0%2C0.0.0.0%2C10.x.x.x%3C%2FP%3E%3CP%3Euse%20%3A%20Route%20Print%20%2C%20ADD%20%26amp%3B%20delete%20method.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

I am using Recovery Services to protect a bunch of our on-prem servers that are on ESXI 6.7. We are having issues with a few of our older machines which are 2008R2, while we are working to get rid of these with our vendor we have found when we do our Test Failovers to Azure, we cannot get the Network to work or the Agent to go into a Ready status. 

 

The machines are running Azure VM Agent ver 2.7.41491.949.

 

Sometimes when I toggle the "Test Connection" under Connect - RDP it seems to jog the system and get it going, but it's not consistent.  I have also tried switching from DHCP to Static and back, changing subnets, doing the redeploy option and these seem to never get it going.

 

These machines have every update in Windows update on them, the firewalls are disabled as we handle that at the network level here, there is no software that would block this. 

 

Any ideas or things that might help with the failover establishing connection?

2 Replies

I would suggest, following fixes might help to consistent network & RDP.

1) Disable NLA ( Azure portal- VM -> Operations -> Run command -> Execute Disable NLA
2) Ensure the VM Network effective route has advertised the On-Prem & Azure network gateway
3) Ensure any persistent route gateway. If any obsolete gateway update to 0.0.0.0,0.0.0.0,10.x.x.x

use : Route Print , ADD & delete method.

 

Thanks!

Will do, thanks so much I will try these now and start testing monday morning 1st thing.

Thanks so much!