It used to be that building a Windows 2003 clustering solution requires huge investment in an external shared storage subsystem - typically Storage Area Network (SAN) or Network Attached Storage (NAS) - as .e of the key pre-requisites. . top of that, you have to struggle with a lot of parameters and configuration settings before a workable infrastructure can even start to take shape.
Windows Server 2008 ships with the iSCSI Initiator (send data piece). Together with a suitable iSCSI Target (receive data piece), this allows virtually any type of, part of or even a file . a disk storage subsystem to be shared over the IP network using industry standard SCSI v2/v3 commands. With iSCSI, inexpensive SAN shared storage solutions can easily be built.
Unfortunately, Windows does not ship with or offer a separate .uation version of iSCSI Target from the String Bean Software acquisition in March 2006. It does come as a standard in Windows Storage Server 2003 R2 though.
What other iSCSI Target can I use then, you may ask? .e option is StarWind iSCSI Target for Microsoft Windows. Developed by the folks over at Rocket Division Software, this full-featured product supports the Windows Server 2008 Failover Clustering feature. You will find detailed white papers in addition to product documentation to help you get started, all backed by a very knowledgeable and helpful support team. Did I mention that a free .uation (”personal”) version is available? I have successfully tested it and recommend that you check it out (as a number of MVP and IT Pros did as well, here and here).
With the iSCSI shared storage in place, it is relatively straightforward to build a Windows Server 2008 Failover Clustering infrastructure. You should begin with the most basic 2 node Active/Passive configuration and add more nodes later. The key is to use the new Validate a Configuration Wizard to verify readiness and suitability, or commonly “fit for use”. The Wizard will execute a series of tests touching vital components from hardware (host/node configuration), network to disk storage. All settings will be “auto-magically” configured if the basic criteria are fulfilled for building a cluster. For deployment in a production environment, all tests must return a PASS if support from Microsoft is required. Although not strictly a requirement, it is recommended that “Certified for Windows Server 2008″ hardware and components are used.
I have built instructional videos that walk through step by step in building a 2-node Windows Server 2008 Failover Clustering solution using iSCSI from scratch. You can construct the environment in a host-based virtualized environment such as Hyper-V or . real physical boxes if you have enough to go around.
Delegates at my clustering seminars gave thumbs up with high praises over traditional text/screen shot style instructions. If you are interested, post a comment with your contact details*. With enough votes, I may just release a version . the blog
* moderated so your personal information will remain private
References:
TechNet: Failover Clustering
StarWind_MSCluster2008.pdf
StarWind_MS_Cluster_part1.pdf
StarWind_MS_Cluster_part2.pdf
StarWind_Hyper-V.pdf
Storage Manager for SANs Step-by-Step Guide (Microsoft)
Windows Server 2008: Failover Clustering with iSCSI
Update:
Failover Cluster Step-by-Step Guide - Configuring a Two-Node File Server Failover Cluster
Failover Cluster Step-by-Step Guide - Configuring a Two-Node Print Server Failover Cluster