Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Wallander
Starting Member
4 Posts |
 Posted - 2013-05-10 : 11:06:47
|
| Hi, I am a SAN administrator, who is getting his hands dirty on the MS SQL administration these days. We have set up a SQL cluster which is on WIndows 2008 Datacenter R2 and running SQL 2008. This is a completely virtualized infrastructure, as Windows hosts are VMs running on VMware 5.0 ESXi. Shared disks are connected for SQL using guest iSCSI initiator(We found this is much easier option than Physical RDMs, as we have 10GB Nics on the ESX servers) Everything worked like a charm for a while and then suddenly we started getting issues that cluster is failing regularly with the Quorum disk lost error. One of the VM is getting out of the Failover cluster all the time and some times the services didn't failover too. Network people don't see anything unusual and windows VM event log is full of Lost quorum disk error. Did anyone see such issues before ? It is very annoying to see clusters failing.Best Regards,W |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-05-10 : 13:49:47
|
| Do you mean it is automatically vMotioning onto a different ESX host?Jack Vamvas--------------------http://www.sqlserver-dba.com |
 |
|
|
Wallander
Starting Member
4 Posts |
Posted - 2013-05-11 : 09:56:19
|
| Hi, No, The VMs stay where they are. That is as expected and that is how it is to be. But the one of the 2 guest VMs which is a part of the Failover cluster looses iSCSI disksIt is very random. Thanks and Regards,W |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-05-12 : 01:56:08
|
| Are the error logs reporting anything?Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
Wallander
Starting Member
4 Posts |
Posted - 2013-05-16 : 07:34:34
|
| It is Full of Cluster network 'Cluster Network 1' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.We have 3 Network1. Heartbeat2. iSCSI3. Server NetworkWhat I have done so far1. Disabled IPV62. Disabled DNS Registration for iSCSI and Heartbeat Networks, they are on L2 Network 3. Disabled CLuster Network communication on the iSCSI NetworkRegards,W |
|
|
|
|
|
|
|
|
Virtualized SQL Servers getting quorum disk lost