help with Hyper V, how to move a VHDX drive onto the san

[chazzy2501]

OK, I've got to create a new virtual appliance for ESET as centos is no longer supported.

 

The upgrade involves making a new virtual machine, this is provided in the form of a vhdx file from ESET. The ESET instructions assume a working knowledge of HyperV The gist is to create a gen1 virtual machine and point to the downloaded VHDX provided.

 

I'll assume if I did this it'd be running from my downloads folder not the SAN. Do I have to create the new VM from the cluster manager (not hyperv manager) but I don't know how to access the SAN storage correctly..

 

I do see "cluster storage" folder in the c drive of the hyper v hosts, this seems to have all the virtual server drives in it. (I assume this is a shortcut or pointing folder) can I just pop the VHDX in here?

 

cheers!

 

I've moved from Vmware to HyperV thanks to Broadcom:(

Edited September 23, 2024 by chazzy2501

[Bedders]

Note: I've used ESET's own VM before on Hyper-V, but we don't use clusters or a SAN, we just replicate VMs from within Hyper-V to another host.

 

The way I did it was to create a virtual machine in Hyper-V to ESET's specifications (Generation 1, with RAM etc. as specified) and not to give it a disk drive. This creates the folder structure I then use.

Then move the downloaded VHDX file to wherever you store disks for VMs - for me, it's a subfolder called 'Virtual Hard Disks' created by Hyper-V under the main folder for each VM.

For example "G:\Hyper-V\Ubuntu-2024\Virtual Hard Disks\OSDrive.vhdx" with the main virtual machine configuration file(s) in "G:\Hyper-V\Ubuntu-2024"

 

Once you've done this, edit the VM in Hyper-V Manager and add an existing disk. Browse to that location.

[broadld]

Hope you got this sorted. If not you need to put the vhdx file on shared storage. Shared storage in a HyperV Failocver Cluster should display in c:\clusterstorage\. There may be multiple volumes if you have different tiers of storage setup. You need to create a VM in Failocver Cluster Manager and attach the disk. If you have already created the VM in HyperV you can protect it with Cluster Manager after. Have a look at this guide from Papercut which covers quite a lot of it. It will also explain it a lot better! https://www.papercut.com/help/manuals/ng-mf/common/cluster-server-2012-2016/#:~:text=In%20the%20Failover%20Cluster%20Manager,the%20virtual%20machine%20up%20on.