I'm getting the same error
- Code: Select all
"[i]A component on the server did not respond in a timely fashion. This caused the cluster resource 'VM NAME' (resource type 'Virtual Machine', DLL 'vmclusres.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.[/i]"
When I look through my cluster logs I can see that this error has been occurring for the last few days, but I hadn't realized. I hadn't realized that the VMs were failing because this is a non-production cluster and I don't have monitoring enable yet to tell me that the VMs have failed and the errors occur in the evening, after the backups, when I'm not working with the system. When I look through my cluster logs I can see that the error was happening for a few days when I first installed Veeam before I chained my backups together.
Having read the post I've linked to above I'm wondering if running backups in parallel with ODX causes the instability. I've now set my backups back to how they were, i.e. chained together and I've deleted the snapshot registry key. It'll be interesting to see if the instability goes away. I'll monitor the logs over the next few days and post back my findings.