0

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.

  • 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 - Yes, which is why you should continue to push Microsoft for a real and permanent solution to your case. We can't help you. – joeqwerty Jan 18 '18 at 15:27
1

The key in your question is "Application Consistent" failing and "Crash Consistent" succeeding. This indicates that VSS is failing or a VSS writer is failing. Microsoft has a number of tools to help you figure out what is failing. This information may not provide you with a solution (often it will), but you will definitely get better attention at Microsoft.

One very simple item to check before: make sure that you have free disk space and free memory. Also I would complete file system checks on each drive. Then reboot and follow the article below.

Review this article on VSS Tracing. This article will describe the tools and how to use them.

VSS Tracing

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.