ASR Replication Issue - Error ID 70171

%3CLINGO-SUB%20id%3D%22lingo-sub-133908%22%20slang%3D%22en-US%22%3EASR%20Replication%20Issue%20-%20Error%20ID%2070171%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-133908%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20I'm%20new%20to%20using%20this%20forum%20so%20hopefully%20someone%20can%20help%20me%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%202%20x%20on-premise%20Hyper-V%20Windows%202012%20R2%20which%20replicate%2010%20servers%20into%20an%20Azure%20Recovery%20Vault%20which%20is%20used%20for%20ASR.%20I%20have%20a%20configured%20ASR%20policy%20which%20has%20been%20working%20for%20most%20of%20the%20year%20with%20no%20issues.%20%3CBR%20%2F%3E%3CBR%20%2F%3EOn%20Thursday%20last%20week%20I%20received%26nbsp%3Bnotification%20to%20upgrade%20my%20Hyper-V%20Hosts%20from%20Azure%20ACS%20to%20AAD%20for%20ASR.%20I%20did%20this%20and%20it%20all%20went%20well%20and%20they're%20on%20Agent%20Ver%20%3CSPAN%20data-bind%3D%22text%3A%20value().text%2C%20visible%3A%20value().isText%22%3E5.1.2700.0%20(latest)%20and%20I%20updated%20the%20MARS%20Agents%20to%20the%20latest%20too%20as%20I%20had%20a%20notice%20about%20these%20needing%20updating%20to%20the%20latest%20version.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3EWhen%20I%20now%20list%20my%2010%20servers%20in%20Azure%20they%20are%20all%20RED%20and%20Replication%20Health%20is%20Critical%20and%20RPO%20column%20is%20blank.%20If%20I%20open%20ALL%20the%20servers%20they%20correctly%20state%20the%20App-and%20Crash%20resistance%20times%20%3A%20so%20why%20are%20they%20RED%20and%20stated%20as%20Replication%20Health%20Critical%20%3F%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20on-premise%20hyper-v%20replications%20says%20all%20is%20working%20and%20I%20used%20this%20article%20to%20check%20the%20finer%20points%20that%20replication%20is%20indeed%20being%20sent%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fsite-recovery-azure-to-azure-troubleshoot-errors%23outbound-connectivity-for-site-recovery-urls-or-ip-ranges-error-code-151037-or-151072%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fsite-recovery-azure-to-azure-troubleshoot-errors%23outbound-connectivity-for-site-recovery-urls-or-ip-ranges-error-code-151037-or-151072%3C%2FA%3E).%20%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20ideas%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-133908%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EData%20%26amp%3B%20Storage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESite%20Recovery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134079%22%20slang%3D%22en-US%22%3ERe%3A%20ASR%20Replication%20Issue%20-%20Error%20ID%2070171%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134079%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EPlease%20refer%20this%20link%20for%20error%20and%20troubleshooting.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fsite-recovery-azure-to-azure-troubleshoot-errors%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsite-recovery%2Fsite-recovery-azure-to-azure-troubleshoot-errors%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20cant%20find%20it%20from%20above%20you%20can%20make%20a%20support%20ticket%20to%20Azure%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi. I'm new to using this forum so hopefully someone can help me

I have 2 x on-premise Hyper-V Windows 2012 R2 which replicate 10 servers into an Azure Recovery Vault which is used for ASR. I have a configured ASR policy which has been working for most of the year with no issues.

On Thursday last week I received notification to upgrade my Hyper-V Hosts from Azure ACS to AAD for ASR. I did this and it all went well and they're on Agent Ver 5.1.2700.0 (latest) and I updated the MARS Agents to the latest too as I had a notice about these needing updating to the latest version.

When I now list my 10 servers in Azure they are all RED and Replication Health is Critical and RPO column is blank. If I open ALL the servers they correctly state the App-and Crash resistance times : so why are they RED and stated as Replication Health Critical ??

The on-premise hyper-v replications says all is working and I used this article to check the finer points that replication is indeed being sent: https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-azure-to-azure-troubleshoot-error...).

Any ideas ?

1 Reply
Highlighted

Hi,

Please refer this link for error and troubleshooting.

https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-azure-to-azure-troubleshoot-error...

 

If you cant find it from above you can make a support ticket to Azure