Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.
Why the VHD file is always shows error?
This is a 2-host MS HyperV 2012 setup, with 8 VMs within. Both hosts are sharing the same SAN Storage, and 2 volumes were created in paths - c:\clusterstorage\volume1 and volume2, respectively. However, whenever I tried to move some of the the VHD (or VHDX) files to different volume or host, the error occurs as attached.
I just took over the administration of the above virtualization setup. I not sure whether this is because both volumes are not CSV, but, does it mean that both volumes have to be converted to be CSV (Clustered Storage Volume)? I check the host resources are enough, what else?
Thanks first, hope you guys could be any help.
EE---MS-HyperV-27000.jpg
I just took over the administration of the above virtualization setup. I not sure whether this is because both volumes are not CSV, but, does it mean that both volumes have to be converted to be CSV (Clustered Storage Volume)? I check the host resources are enough, what else?
Thanks first, hope you guys could be any help.
EE---MS-HyperV-27000.jpg
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Volume1 and Volume2 are Cluster Shared Volumes.
Any additional LUNs that are hooked into the two nodes must have the Add Cluster Storage step run then Add to Cluster Shared Volumes.
Once they are in CSV, you'll see Volume3 and Volume4 ETC.
In Failover Cluster Manager use the Storage Live Migration process to move the VHDX files from their current CSV to a new one. This can be done so the VM does not have to be taken offline.
Any additional LUNs that are hooked into the two nodes must have the Add Cluster Storage step run then Add to Cluster Shared Volumes.
Once they are in CSV, you'll see Volume3 and Volume4 ETC.
In Failover Cluster Manager use the Storage Live Migration process to move the VHDX files from their current CSV to a new one. This can be done so the VM does not have to be taken offline.
Hi Philip Elder,
On my second visit, found that all 3 volumes are already CSV. However, I found out 2 new things:
1st, the VHD file is "somehow" attached to the different host in Disk Manager. After "detach" the VHD, and I can rename/move the it.
2nd, attempt to "live migration" any of the VM still failed. Found the cluster network could be the culprit. There are 2 cluster networks, cluster network 1 have both nic1 of host1 and host2 for private traffic. However, cluster network 2 only have host2 component for vSwitch.
Both host1 and hosts are configured with same vswitch name, but, only host2's one is listed. I'll scheduled to re-create vswitch on host1. Since this needs downtime, so, I have scheduled to get it done tomorrow. Please see my update.
On my second visit, found that all 3 volumes are already CSV. However, I found out 2 new things:
1st, the VHD file is "somehow" attached to the different host in Disk Manager. After "detach" the VHD, and I can rename/move the it.
2nd, attempt to "live migration" any of the VM still failed. Found the cluster network could be the culprit. There are 2 cluster networks, cluster network 1 have both nic1 of host1 and host2 for private traffic. However, cluster network 2 only have host2 component for vSwitch.
Both host1 and hosts are configured with same vswitch name, but, only host2's one is listed. I'll scheduled to re-create vswitch on host1. Since this needs downtime, so, I have scheduled to get it done tomorrow. Please see my update.
In Failover Cluster Manager under the Storage node you should see OWNER for each CSV. That's why the disk shows up on one node and not the other. The cluster service takes care of arbitrating calls to the storage via the OWNER.
Before doing anything please post the following via elevated PowerShell in a TXT file from each node:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMHardDiskDrive * | FL
Before doing anything please post the following via elevated PowerShell in a TXT file from each node:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMHardDiskDrive * | FL
Hi Philip Elder,
The new vswitches were created on HyperV01 host, still the "live migration" issue persists. Please see my further actions recreating the new VM to replace the existing VM as follows:
a. Open Cluster Mgr, select existing VM1, click to shut down
b. right-click and then select the properties of the existing VM1:
- Jot down vCPU, vRAM, IP
- path of the existing vHDD1, vHDD2,...
- jot down the vswitch
c. rename VM1 as VM1old
d. In Cluster mgr, select to create new VM, name it as VM1 and then next:
- select which host to house the new VM
- select existing HDDs as the information got from b.; same for vCPU and vRAM
- select the new location to house all the vHDDs, VM stuff
- click Next until finish
- Power up this new VM
e. Log on to this new VM1, check for hostname, IP, partitions, etc
f. In Cluster mgr, right-click VM1old, and then select to remove
g. Open hyperv mgr, right-click VM1old, and then select to remove
After that, try live migration from hyperv01 to/fro hyperv02, it works.
The new vswitches were created on HyperV01 host, still the "live migration" issue persists. Please see my further actions recreating the new VM to replace the existing VM as follows:
a. Open Cluster Mgr, select existing VM1, click to shut down
b. right-click and then select the properties of the existing VM1:
- Jot down vCPU, vRAM, IP
- path of the existing vHDD1, vHDD2,...
- jot down the vswitch
c. rename VM1 as VM1old
d. In Cluster mgr, select to create new VM, name it as VM1 and then next:
- select which host to house the new VM
- select existing HDDs as the information got from b.; same for vCPU and vRAM
- select the new location to house all the vHDDs, VM stuff
- click Next until finish
- Power up this new VM
e. Log on to this new VM1, check for hostname, IP, partitions, etc
f. In Cluster mgr, right-click VM1old, and then select to remove
g. Open hyperv mgr, right-click VM1old, and then select to remove
After that, try live migration from hyperv01 to/fro hyperv02, it works.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial