May 20, 2020 at 5:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
June 9, 2020 at 10:31 am
The behavior you are describing is a successful drain operation. When the drain action is started for the cluster all resources are moved to a different node. This results in a restart of the SQL Engine on another node. Probably, there will also be a second restart for the fallback-operation after maintenance has finished.
June 9, 2020 at 2:55 pm
Thanks for the reply 🙂
So then, how can you tell the difference between when the drain operation is working, and when it's not? Are there attributes in the SQL Server error log I can look for, or should I be looking in the Windows event log, or perhaps there's a Windows Cluster Services log I could look into? I am a reticent to move to a new policy of allowing a restart of cluster nodes earlier in the day, if I can't verify that it's working.
Thanks,
--=Chuck
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply