euphony
Contributor
Contributor

Windows Server 2008 Clustering

Jump to solution

I am testing Windows Server 2008 clustering witj shared storage on an IBM ds4500 SAN. Two RAW LUNs are being used as a shared storage on two Windows Servers 2008. When I run a validation test as a part of setting up a cluster I ger errors on the Disk validation. As a result no disks are found which are suitable for server 2008 clustering. The error in the log is as follows:

"LSI Adapter, Ultra320 SCSI 2000 series, w/1020/1030 False Disk bus type does not support clustering. Disk partition style is MBR. Disk partition type is BASIC."

If I add the same two RAW Luns for Windows Server 2003 clustering they are valid disks presnted to set the cluster.

Has VMware esx 3.5 update 2 has support for setting up 2008 clustering ?

Thanks

R

0 Kudos
1 Solution

Accepted Solutions

Hi,

For win2k8 MSCS support you require two things

1) SCSI 3 persistent reservation

2) Virtual SAS device

Both of these are still not supported on 3.5.

Thanks,

Samir

Blog : http://thinkingloudoncloud.com || Twitter : @kooltechies || P.S : If you think that the answer is correct/helpful please consider rewarding points.

View solution in original post

0 Kudos
10 Replies

Hi,

Win2k8 Clustering is still not supported on ESX 3.5 versions , as it uses the SCSI 3 protocol. So this setup is not going to work as of now on a 3.5 environment with win2k8.

Thanks,

Samir

P.S : If you think that the answer is helpful please consider awarding points

Blog : http://thinkingloudoncloud.com || Twitter : @kooltechies || P.S : If you think that the answer is correct/helpful please consider rewarding points.
0 Kudos
euphony
Contributor
Contributor

Hi,

Thanks. I also found out that w2k8 clustering needs serial attached SCSI (SAS), iSCSI, and Fibre. You mean to say that the LSI Logic SCSI Controller I am using in VM on esx3.5 does not support SCSI-3 commands?

R

0 Kudos

Hi,

For win2k8 MSCS support you require two things

1) SCSI 3 persistent reservation

2) Virtual SAS device

Both of these are still not supported on 3.5.

Thanks,

Samir

Blog : http://thinkingloudoncloud.com || Twitter : @kooltechies || P.S : If you think that the answer is correct/helpful please consider rewarding points.
0 Kudos
euphony
Contributor
Contributor

even on esx 3.5 update 3?

Thanks

R

0 Kudos

Hi,

Yes even on 3.5 U3.

Thanks,

Samir

Blog : http://thinkingloudoncloud.com || Twitter : @kooltechies || P.S : If you think that the answer is correct/helpful please consider rewarding points.
0 Kudos
Texiwill
Leadership
Leadership

Hello,

Moved to Virtual Machine and Guest OS forum.


Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
abaum
Hot Shot
Hot Shot

Minor clarification: W2K8 clustering IS supported in Vmware. You just can't use shared storage due to SCSI-3 limitations mentioned above. We use W2K8 clusters for Exchange, but instead of shared storage, we use a witness quorum and CCR.

adam

0 Kudos
euphony
Contributor
Contributor

What will be the work around to use shared storage in w2k8 clustering for SQL databases? Can you direct me to a good document on w2k8 clsuter for exchange?

Thanks

R

0 Kudos
abaum
Hot Shot
Hot Shot

There is no workaround for shared storage. Probably won't be until Vmware 4 (or whatever the new name is). As for good documentation on Exchange clustering, there are a few guides on VM's site and on MS's site. The basic gist is to just use clustering for the Exchange service. Disks are unique to each guest so use CCR to replicate between the two. I think the MS guide also says to not use HA/DRS with them. Sort of defeats the purpose of clustering if both nodes end up on one host. Rather than turn of HA/DRS, we just created DRS rules that say to keep the two guests separate.

http://www.vmware.com/solutions/business-critical-apps/exchange/

http://blogs.vmware.com/vmtn/2008/03/16000-exchange.html

adam

0 Kudos
euphony
Contributor
Contributor

excellent !

I will try setting up an exchange cluster environment then.

Thanks for your help

R

0 Kudos