Hi All,
I have identified a bug in the copy cluster roles wizard in 2012 R2, which is preventing me from migrating my clusters from 2008 R2 & 2012 to 2012 R2.
The bug surfaces when you attempt to copy a VM role from a 2008 R2 or 2012 cluster that has a CSV reparse point name that contains spaces as follows:
The role appears to copy across fine, but once you've migrated the CSV and brought it online followed by starting the VM, the VM configuration resource promptly fails along with the VM.
The issue can be spotted inside the copy cluster roles wizard, where it presents itself by removing all text after the first space in the name to read "C:\ClusterStorage\CSV" rather than "C:\ClusterStorage\CSV Test Disk 3" as follows:
The bug only appears for VMs on CSVs with a reparse point name containing spaces - all other scenarios succeed.
After searching through the registry on the new cluster, you can clearly see that the VM role hasn't been correctly copied.
It shows a value called SharedVolumeMappings with the data C:\ClusterStorage\CSV|<guid>|<integer>
Whereas it should show the data C:\ClusterStorage\CSV Test Disk 3|<guid>|<integer>
If you modify the data in the SharedVolumeMappings value in both0.Cluster\Resources\<VM guid> and Cluster\Resources\<VM guid> keys, the VM will start and work correctly.
The problem for me is that I have many VMs on many different CSVs all with spaces in the names of the reparse point! Its not feasible for me to go through the registry for every copied VM on every node of the new cluster, as this would take a very long time and would be prone to errors that could cause further problems.
Can anyone provide any help on this? A hotfix for the issue would be great, if anyone from Microsoft is reading :-)
My deadline to get the VMs migrated to the new cluster is the 21st February, so I would really like to have a solution to the problem before then if at all possible.
Many thanks in advance,
Tom