Azure Site Recovery issues with Hyper-V Integration tools

%3CLINGO-SUB%20id%3D%22lingo-sub-146294%22%20slang%3D%22en-US%22%3EAzure%20Site%20Recovery%20issues%20with%20Hyper-V%20Integration%20tools%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146294%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Community%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20dealing%20with%20an%20issue%20for%20sometime%20now%20which%20is%20that%20Domain%20Controllers%20Virtual%20Machines%20that%20are%20replicated%20to%20Microsoft%20Azure%20using%20the%20Azure%20Site%20Recovery%20service%2C%20are%20failing%20to%20take%20Application-Consistent%20snapshots%20while%20they%20can%20take%20Crash-Consistent%20snapshots%20normally.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOf%20course%20prior%20setting%20everything%20up%2C%20I%20have%20ensured%20Microsoft%20supports%20replicating%20production%20Domain%20Controller%20VMs%20from%20premises%20to%20Azure.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAll%20the%20environments%20in%20where%20the%20issue%20occurs%20consist%20of%20Windows%20Server%202012%20R2%20Hyper-V%20hosts%20and%20the%20guest%20VMs%20are%20Windows%20Server%202012%20R2.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20note%20all%20VMs%20are%20running%20only%20AD%20DS%2FDNS%20services%20as%20workloads%20thus%20the%20possibility%20of%20conflict%20with%20additional%20installed%20software%20nearly%20gets%20eliminated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20confirmed%20that%20there%20is%20a%20specific%20pattern%20followed%20when%20the%20issue%20occurs%20which%20is%20that%20NTDS%20writer%20is%20always%20in%20failed%20and%20non-retryable%20state%20and%20relevant%20failure%20events%20are%20always%20logged%20in%20Event%20Viewer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESince%20this%20issue%20is%20recurring%2C%20I%20have%20logged%20a%20ticket%20with%20Microsoft's%20support%20but%20while%20it%20had%20been%20escalated%20numerous%20times%20the%20only%20answer%20I%20got%20was%20to%20uninstall%20the%20Hyper-V%20integration%20Tools%20from%20the%20affected%20VMs%20and%20see%20what%20happens.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20what%20happens%20once%20Integration%20Tools%20get%20uninstalled%20from%20the%20affected%20VMs%2C%20the%20Application-Consistent%20snapshots%20are%20being%20taken%20successfully%20however%20once%20VMs%20install%20Windows%20Updates%20and%20restart%2C%20the%20Integration%20Tools%20will%20reinstall%20their%20selves%20once%20again%20resulting%20to%20the%20very%20same%20issue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20question%20is%20why%20does%20this%20happen%3F%20Is%20it%20a%20known%20bug%20or%20something%20Microsoft%20is%20aware%20of%3F%3C%2FP%3E%0A%3CP%3EEven%20if%20permanently%20uninstalling%20Integration%20Tools%20and%20ensuring%20they%20won't%20be%20installed%20again%20(if%20that's%20possible)%20resolves%20the%20issue%20I%20think%20the%20community%20has%20to%20get%20an%20official%20answer%20from%20Microsoft%20for%20the%20root%20cause%20of%20the%20issue%20as%20well%20as%20for%20its%20resolution.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFinally%2C%20despite%20I%20didn't%20find%20any%20relevant%20issue%20posted%20on%20the%20internet%20I%20have%20the%20sense%20that%20many%20others%20will%20be%20dealing%20with%20this%20issue%20so%20I%20hope%20if%20this%20get%20resolved%20to%20help%20others%20in%20the%20future%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-146294%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
Regular Visitor

Hi Community,

 

I am dealing with an issue for sometime now which is that Domain Controllers Virtual Machines that are replicated to Microsoft Azure using the Azure Site Recovery service, are failing to take Application-Consistent snapshots while they can take Crash-Consistent snapshots normally.

 

Of course prior setting everything up, I have ensured Microsoft supports replicating production Domain Controller VMs from premises to Azure.

 

All the environments in where the issue occurs consist of Windows Server 2012 R2 Hyper-V hosts and the guest VMs are Windows Server 2012 R2.

 

Please note all VMs are running only AD DS/DNS services as workloads thus the possibility of conflict with additional installed software nearly gets eliminated.

 

I have confirmed that there is a specific pattern followed when the issue occurs which is that NTDS writer is always in failed and non-retryable state and relevant failure events are always logged in Event Viewer.

 

Since this issue is recurring, I have logged a ticket with Microsoft's support but while it had been escalated numerous times the only answer I got was to uninstall the Hyper-V integration Tools from the affected VMs and see what happens.

 

Now what happens once Integration Tools get uninstalled from the affected VMs, the Application-Consistent snapshots are being taken successfully however once VMs install Windows Updates and restart, the Integration Tools will reinstall their selves once again resulting to the very same issue.

 

My question is why does this happen? Is it a known bug or something Microsoft is aware of?

Even if permanently uninstalling Integration Tools and ensuring they won't be installed again (if that's possible) resolves the issue I think the community has to get an official answer from Microsoft for the root cause of the issue as well as for its resolution.

 

Finally, despite I didn't find any relevant issue posted on the internet I have the sense that many others will be dealing with this issue so I hope if this get resolved to help others in the future as well.

0 Replies