Quick Tip – When Copying VHDs to a CSV Disk – Use The Disk Owner!
Cluster Shared Volumes (CSV) is a new feature that was introduced in Windows 2008 R2.
If you want to read more about it, how it works, and how you can enable it. There is a lot of material out there that you can refer to:
- Windows 2008 R2 NLB & Failover Clustering
- http://technet.microsoft.com/en-us/library/dd759255.aspx
- http://technet.microsoft.com/en-us/library/dd630633(WS.10).aspx
- http://blogs.msdn.com/clustering/archive/2009/03/02/9453288.aspx
- http://blogs.msdn.com/clustering/archive/2009/02/19/9433146.aspx
Well, after you’ve setup your cluster, enabled CSV, and added clustered disks to CSV, it is now time to copy your VHD files to those CSV disk. The big question is, which cluster node should you perform this operation on?
We’ll, to make a long story short – Copy it to the node that owns the CSV disk!
The reason this is important is that if you are running the copy on the coordinator node (the node which owns the CSV volume of interest), the writes are all local writes. If you are running the copy on any other node, the writes are actually redirected over the network (because they are extending writes to the file) and not done directly to the volume.
Hope this will save you some much needed time
Related posts:

What do you mean by “not done directly to the volume”? Does that mean the writes are saved but io is just slower?
Also – why should copying be any different than the actual production running of the VMs? If I have a single CSV volume among (for example) two nodes in my cluster, each node running half of my total number of VMs, are you saying that is bad, and that I should have two seperate CSV volumes, one dedicated for each node?
Thanks for the feedback Reuvy.
A couple of days after my post, NetApp has also published a post on this subject at their blog. It contains more details about what I wrote – http://blogs.netapp.com/msenviro/2009/12/file-operations-on-csvs-part-one.html
Check it out, and if something is still not clear, feel free to contact me.