We help IT Professionals succeed at work.

Windows Server 2008 iSCSI Failover Cluster

Medium Priority
Last Modified: 2012-08-14
I'm in the process of creating a iSCSI Failover Cluster in Windows Server 2008.  My process so far, has been the following:

1.  Present the LUNs to Node A and Node B.
2.  Shutdown Node B.
3.  Configure the Microsoft iSCSI Software Initiator on Node A.
4.  Bring the disks online, initialize, and format the disks.
5.  Shutdown Node A.
6.  Power on Node B.
7.  Configure the Microsoft iSCSI Software Initiator on Node B.
8.  Bring the disks online.
9.  Shutdown Node B.
10.  Power on Node A.
11.  Validate the cluster configuration by using "Validate a cluster."  It was successful.
12.  Create the cluster.
13.  Add all iSCSI cluster disks to the cluster.
14.  Power on Node B as Node A has ownership of the clustered disk.

Node B hangs upon logging in.  Event Viewer indicates that Node B is trying to access the shared clustered disks.

Am I setting this cluster up incorrectly?  

Any ideas or recommendations?  
Watch Question

The iSCSI disk in use, does it support clustering and and Cluter Supporting File System? If not, Node A may have a lock on the filespace.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.