Avatar of Trivita
Flag for United States of America asked on

Hyper V / FCM CSV migrations

I have a Server 2008 r2 sp1 Hyper V 2 node cluster. All software is up to date.
We are connected to our Netapp SAN via iSCSI.
Historically we had our Virtual guests in a 1:1 vol/lun ratio, each volume on our storage contained 1 lun and each lun had a unique drive letter assigned to it.
As the story goes we started to run out of drive letters so I researched Cluster Shared Volumes and liked what I found so I implemented them. The CSV config went well and we are running 25% of our VM's on CSV's. I can move and live migrate the 1:1 vol/lun VM's we have, but are looking to upgrade everything to CSV.

The problem I am having is moving or Live Migrating the CSV's. The CSV VM's fail at the end of the migration and Move back to the host I was trying to move them from. The only way I can move the CSV's is to shutdown > move > start. In Failover cluster manager I think the failure happens because the "Current Owner" under Cluster Shared Volumes does not change.

I have tried both from SCVMM and Failover Cluster Manager same result with both.
I have added dedicated Live Migration NIC's and set the metrics and roles on all nics appropriately.
All Networks in FCM have the same name.

I have exhausted my novice CSV knowledge and would appreciate any help!

thank you
Microsoft HardwareMicrosoft Virtual ServerWindows Server 2008

Avatar of undefined
Last Comment

8/22/2022 - Mon

Normally this is caused by problems with the virtual network names. You can test this out by taking a VM and disconnecting it from all networks and then try to live migrate it. If it works, then your problem is in the virtual network configuration, in which case I usually rebuild all of the virtual networks on all hosts. The CSV owner normally doesn't ever change unless the owner is rebooted, or you manually switch it.

FWIW, I don't use any dedicated live migration or cluster networks. I configure networking for my hosts and then whatever virtual networks I need for VM configuration.

I removed the virtual network
Tried every scenario Move/ Quick Migration/ Live migration
Each attempt failed, the only way I can successfully migrate is if im migrating to the owner (host) of the CSV.

Added the virtual network back and got the same results.

I found an interesting article

The Using Hyper-V with CSV storage section of the document states to add following paths to hyperv manager > ...

C:\ClusterStorage\Volume1\Hyper-V\Virtual Hard Disk

1. We have 10 volumes under CSV, can the path just be C:\ClusterStorage ?
2. Since we have both regular virtual guests and CSV guests on the same highly available host environment, a path is already in the Hyper-V settings for VHD and VM locations...below

-C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks  (this location has no data in it so doesn't look like an issue if I change it)
-C:\ProgramData\Microsoft\Windows\Hyper-V                      (this location has data that has today's date...like it is being used)

I am just afraid that if I change what appears to be a global setting i will break the non CSV vm's.

The configuration data for your CSV based VMs needs to be under c:\clusterstorage\CSVVolumeName . If it is under anything else, those files are not available to other nodes in the cluster. The snapshot file location should also be there.

You may need to use SCVMM to migrate the storage of the VMs to the C:\ClusterStorage\Volume1 CSV path. Why do you have so many CSVs? Are you just converting your old LUNs without consolidating them?

You can't have things under just c:\clusterstorage because that is the root of the mount points to the CSV volumes.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy

I have attached a file with some screen shots and questions...

The attachment also contains answers to your questions...

Thank you for your continued support

I don't see any attachments.

Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.

The screen shots of Volume2 look okay. You only have 1 VM there, which defeats the main benefits of CSV which is to have many VMs on a single volume. The ClusterHBFile is used for coordinating access to the files on the CSV, I believe.

As long as everything is under VolumeX, you are okay.

The two things that I can think of that would prevent a Live Migration are incompatable network names, and processor incompatability. Have you made sure that the processor compatability option is checked under the processor section of the VM? Your servers are ALL Intel or ALL AMD, right? What happens if you try to do a quick migration?

FYI, I will be generally unavailable until Tuesday.

I have triple checked the network names.
Verified the procs are all the same on the dell PE 2950's
I have checked the proc compatibility option...did not fix.

Quick and Live migration both fail.
It appears they fail right at the end when they try to turn on the vm or activate memory pages on the other host.

To add a side note, we have VM's that existed pre R2 so they have not been migrated to CSV's. These non CSV VM guests Live Migrate without a problem.

About to call Microsoft since I have reached the end of the internet trying to find a solution. I will update the ticket if they find the issue.
But by all means respond if you want me to try anything else you can think of.

thank you for your continued support!

Just so I am clear, if you take a VM that you can not Live Migrate or quick migrate, if you shut it down, you can migrate it? Very strange.
Your help has saved me hundreds of hours of internet surfing.

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

where my points at?

Wow, that was a lot of troubleshooting. I haven't gotten to the point of getting Sophos to run on my Hyper-V Server hosts, so I guess that has saved me. Files on CSV are different because the drive never detaches from the hosts, which may be causing the problems...maybe Sophos is trying to hold onto the files?

because it working
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.