A few months Bruce Langworthy wrote an excellent article regarding some new recommendations for setting the Windows Disk Timeout value - http://blogs.msdn.com/b/san/archive/2011/08/15/the-windows-d...
Updated Jul 01, 2019
Version 2.0
Blog Post
Really good article, thank you!
Just a question: I am seeing this exact behaviour in one of my DAG members when I run backups on it. However, the server does not host any active databases (and you mentioned “(...) is affecting active databases on a DAG node”) and the server becomes completely unresponsive... It stops processing further backup jobs, unable RDP or login, but able to PING server... The only way of recovering is by rebooting the server using the VMware Console.
If the server is hosting active databases, they don’t even failover to another DAG member...
Is this the expected behaviour?
Thank you!