重复VM意外重新启动-事件41任务63内核电源 [英] Repeat VM unexpected reboot - Event 41 Task 63 Kernel Power
问题描述
仅第二次出现此问题.安装程序是运行SQL Server 2016的Windows Server 2016. 2个节点群集，4个可用性组.
Just had the second occurrence of this issue. Setup is Windows Server 2016 running SQL Server 2016. 2 node cluster, 4 Availability Groups.
在没有警告的情况下，AAG主VM上出现此错误，它崩溃了……并设法破坏了该过程中的数据库.
With no warning got this error on the AAG Primary VM and it went down...and managed to corrupt a database in the process.
系统已重新启动，而没有先关闭系统.如果系统意外停止响应，崩溃或断电，则可能导致此错误.
| <表格> <身体> | ||
| - | 提供者 |
推荐答案
接下来转到VM的Metrics选项卡.在虚拟机上检查读/写拜拜，以检查节流情况 Next go to the Metrics tab of the VM. Check the Read/ Write byes on the VM to check for throttling
如果您正在运行SQL计算机，则通常重新启动的原因是限制.您将要确保遵循SQL最佳做法指南 If you are running a SQL machine often the reason for reboots is throttling. You will want to make sure you are following the SQL Best practices guide 这将包括具有正确的磁盘大小和VM大小以支持负载. This will include having the correct disk sizes and VM size to support the load. 您还可以检查VM的系统日志.搜索在重新启动期间可能发生的所有错误检查.这表明来宾操作系统存在问题，需要解决. You can also check the system logs of the VM. Search for any Bug Checks that might have happened around the time of the reboot. This will indicate an issue with the Guest OS that will need to be addressed. 如果以上所有方法都没有产生任何问题，那么我建议您打开支持通知单以让后端工程师查看. If all of the above does not yield any issues then I would suggest opening a Support ticket to have the backend engineers take a look. 我怀疑问题与节流或错误检查有关.因此，请报告您在此处看到的任何内容:) I suspect the issue to be with Throttling or a bug check. So report back on anything you see there please :) 这篇关于重复VM意外重新启动-事件41任务63内核电源的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取
|
15天全站免登陆
|