We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Cluster Shared Volume issue

iris01
iris01 asked
on
Medium Priority
1,362 Views
Last Modified: 2012-05-11
Hi All

I have a strange problem with a 3-node server 2008 r2 failover cluster running in a node majority quorum configuration with an iscsi SAN. I can't get cluster shared volumes to work correctly. I set up 1 disk on the SAN and create the CSV from that, which is visible and accessible from all 3 nodes. I set up a VM on this CSV on the first node and it runs fine, but when attempting to move/migrate the VM to another node it fails with a fairly generic "Cluster resource 'X' in clustered service or application 'Y' failed", followed by "The Cluster service failed to bring clustered service or application 'Y' completely online or offline, one of more resources may be in a failed state". If however I change the owner of the CSV first, the VM will move fine. My understanding of CSV is that it shouldn't matter who the owner of the CSV is, all the nodes should be able to access it?

If I destroy the cluster and instead set it up by assigning the SAN disk a drive letter through disk management, then create the cluster without using CSV, moving/migrating a VM works fine as the disk will move with it automatically. I really can't see what the problem is.

I attach an ipconfig from the three nodes as I suspect this is probably a networking thing, though the hyper-V virtual network is named identically on all 3, and File sharing / client for microsoft networks is enabled.

Thanks in advance for any assistance.
ipconfig.txt
ipconfig2.txt
ipconfig3.txt
Comment
Watch Question

Felix LevenSenior System and Databaseadministrator

Commented:
Attached Drives in the moved VM (passthrough HDD, DVD-Rom, Images) can cause trouble when migrating from one node to the other!

Author

Commented:
Thanks, but the VM's are blank / no OS, plus they work fine when the disks aren't in CSV
Felix LevenSenior System and Databaseadministrator

Commented:
Startup action -> no action?
Felix LevenSenior System and Databaseadministrator

Commented:
no default gateway recommended for the cluster network

Author

Commented:
The VM is set to auto-startup, if that's what you mean?

There is no default gateway in place, or are you saying that there should be?
Felix LevenSenior System and Databaseadministrator

Commented:
Microsoft Failover Cluster Virtual Adapter, no default is OK

There is an option for the VM on startup: no action -> this should be used for live migration and CSV

and no ISO mounted even on a blank VM.

Author

Commented:
Thanks again, but these things aren't my issue, the VM works fine for move/migration when I set the disks up without using csv.
Felix LevenSenior System and Databaseadministrator

Commented:
You have full local access to the CSV from all three cluster-nodes?

you changed the owner to ?

Author

Commented:
Yes I can access the CSV from all nodes, seem to be able to read and write fine with test files.

In order to move the VM from node 1 to node 3, for example, I first move the CSV disk to be owned by node 3, then move the VM
Felix LevenSenior System and Databaseadministrator

Commented:

Author

Commented:
These things don't seem to apply (I've read them all already), I can access (read/write) the shared volumes from any node, but VM's aren't able to boot unless their current node owns the volume.

I did try disabling the cluster iscsi networks as in the second link, but no change.
Felix LevenSenior System and Databaseadministrator

Commented:
Did you create your <systemdrive>\ClusterStorage folder before you enabled the Cluster Shared Volumes ?

Author

Commented:
No
Felix LevenSenior System and Databaseadministrator

Commented:
Strange, last thing i can think of is an error in the management console, SP1 on the R2 servers or check the node in powershell with Test-Cluster -Node myserver?

Author

Commented:
Checking the node didn't tell me anything useful, and I shouldn't have to use SP1 to get this working, nor would I expect different behaviour if I do install it

Anyone else got any ideas?
Felix LevenSenior System and Databaseadministrator

Commented:
and File sharing / client for microsoft networks is enabled.

"Client for Microsoft Network" and “Microsoft File & Print Sharing" need to be enabled

Default virtual Disk & configuration location is set to the CSV ?

Author

Commented:
Yes all enabled, and everything is pointed at the CSV, otherwise I don't think it would move even after changing the owner of the volume
Felix LevenSenior System and Databaseadministrator

Commented:
Same error was reported on the FreeNas Forum, iSCSi worked fine without CSV but failed with the same error message you had.

http://sourceforge.net/apps/phpbb/freenas/viewtopic.php?f=53&t=5027

Author

Commented:
Thanks for that, it's not quite the same issue, I can move the CSV between nodes fine, I just can't move the VM's without first moving the CSV, which seems to defeat the point of them
Felix LevenSenior System and Databaseadministrator

Commented:
CSV access is all managed by the "CSV coordinator role" owned by one of your three nodes (this is different from you working scenario).
If you create a VM through the Failover Cluster Manager the configuration is updated, anytime you re/configure a VM in Hyper-V Manager, you have to update the cluster config in Failover Cluster Manager.
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
No solution found
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

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

OR

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.