none
vhd paths in Hyper-V Manager and Failover Cluster Manager

    Question

  • Hello Everyone,

    Yesterday I was doing some storage migration in the cluster. I added some 3PAR storage to my environment and wanted to migrate the VMs from the volumes of the HITACHI disks we have to 3PARs. We migrated the vhd files of the VMs to the 3PAR before we added 3PAR to the cluster, changed the path of the vhd files of the VMs to the 3PAR volumes, and then we added the 3PAR to the existing HITACHI cluster. Everything went smooth, and the Hyper-V manager was showing the new volume for the VMs. I powered on all the VMs and they were running smooth also. The only thing that I was concerned, was Failover Cluster Manager, because the VMs in  services and application were not reflecting the new volume that I assigned to those VMs. It was still showing the path of the old volume of the HITACHI disks.

    Since it is a service and application, I understand that the new volume is now operating in the 3PAR, and is not showing the right path,  but is it something that I have to configure or anything I should do to reflect the new volumes in the Failover Cluster Manager, cause I'm not very experienced with VMs environment.

    Thank you

    Enion

    Wednesday, January 25, 2017 5:54 PM

All replies

  • Now that you have done that, there was a better way to have done it.

    You should have added the storage to the cluster first and simply used the storage migration option.  Everything would have been 'fixed' using the tools meant for this task.

    Also, since you are talking about paths to 3PAR and Hitachi disks, how have you configured the storage within the cluster?  Did you configure the storage as simple cluster disks or as Cluster Shared Volumes (the recommended way)?


    . : | : . : | : . tim

    Wednesday, January 25, 2017 7:27 PM
  • Now that you have done that, there was a better way to have done it.

    You should have added the storage to the cluster first and simply used the storage migration option.  Everything would have been 'fixed' using the tools meant for this task.

    Also, since you are talking about paths to 3PAR and Hitachi disks, how have you configured the storage within the cluster?  Did you configure the storage as simple cluster disks or as Cluster Shared Volumes (the recommended way)?


    . : | : . : | : . tim

    I didn't have the tools to migrate the storage in the cluster. The VMs where all Windows Server 2008 R2, and the only tool to migrate the storage was Quick Storage Migration, which I couldn't provide that moment. The other thing is that when I was trying to bring the 3PAR disks online in the cluster, before the storage migration, somehow they wouldn't come up online. So I decided to do the migration before adding the 3PAR to the cluster, and then join the cluster of HITACHI.

    Regarding the second question, about the configuration of the storage, it is configured as Cluster Shared Volumes.

    My only concern is that, why is the failover cluster manager, under services and applications, showing the path of the VMs are pointing to the old volumes of hitachi, even though I know that the VMs are standing on 3PARs.

    Wednesday, January 25, 2017 8:12 PM
  • When you say 'path of the VMs are pointing to the old volumes of Hitachi' do you mean that the Settings of the running VM are pointing to C:\ClusterStorage\Volumex and that Volumex is pointing to a specific Hitachi disk?

    . : | : . : | : . tim

    Wednesday, January 25, 2017 10:50 PM
  • Hi,
    Are there any updates on the issue?
    You could mark the reply as answer if it is helpful.
    Best Regards,
    Leo

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 7, 2017 2:25 AM
    Moderator