Hi all,
We have a Hyper-V Cluster of 9 Nodes, connect to a SAN Dell.
By the time the cluster has implemented the person who configures it didn't make the disks volumes (volumes of a physical disk in disk management), Cluster Shared Volumes and SAN Luns names to match through the infrastructure.
For example, I have a LUN named LUN_01, LUN_02, and LUN_03, all with 3TB size created in Unity SAN.
In the Windows Server DIsk management, the Volume labels are named LUN_00, LUN_01, and LUN_BKP.
Its the same for the Cluster Shared Volumes/Disks in the cluster management console.
This is not correct in my opinion the names in servers and cluster should match the names on LUN so we can know for sure we are touching in the right LUN and not have to match LUN IDs from computer management and LUN host access, makes it easy to work and identify the components we are changing.
We needed to increase size on a LUN and we take a long time to understand which was the LUN don SAN to resize.
I know I can change the name in the cluster management console in the proprieties of the cluster disks, and for the volume of the disk, I can also change it via Disk Management console.
But I think when I change the volume name of the disk it will break the VM connection since the VM is expecting his files at C:\ClusterSharedVolume\LUN_BKP and I will change it to C:\ClusterSharedVolume\LUN_03.
- Can I do these changes in an easy way like change the names in Cluster management and Disk management? Any tips?
- How can I do this change safely and without the downtime of VMs or any service of the cluster?
- Does the name of the symbolic links on C:\ClusterSharedVolume* change alone?
- What are the concerns about this change/operation in production?
Did I expose my doubt clear, or it's messy?
Thanks in advance Guys.
Kind Regards
MP