Hi all,
(For below, all OS is 2008 R2 enterprise)
I currently have an HP P2000 G3 iScsi SAN
VM's are hosted on one standalone HyperV server and on High availability Hyper-v cluster server. Storage is network based via i-scsi.
We recently had to recover our exchange server to a VM and my main problem at the moment is the amount of time it takes to back up the standalone VM. Also, I would like to move as many of the VM's as I can to the cluster. For obvious reasons.
Unfortunately all vDisks on the SAN are nearly fully occupied at the moment. To start with I need to move my Exchange VM to the Cluster. The VM (and VHD files) is located on a 2TB Raid volume on the SAN and the VM data is approx. 1.3 TB. iscsi
initiated with a drive letter on the Hyper-v host. Pretty simple.
Cluster already has 2 x VM's hosted and has CSV enabled. 3 x "ClusterStorage Volumes" exists for the current VM's, Live migration works a charm and all redundancy's in place.
Plan would be to Export VM complete from the current Hyper-v onto suitable storage. Then remove the explicit mapping on the SAN to the current Hyper-v, removing the data drive, and then simply add explicit mapping to the 2 x physical nodes of the cluster.
Then in cluster manager add Disk and finally add as cluster volume. Easy.
Would like to know:
Will the partition on the affected RAID volume stay intact? AND if so would it be in any way recommended to skip the 'export' of the VM, and rather just create a new VM on the cluster manager with the same settings and just adding the .vhd files
as drives on the same virtual ide ports as it was on the old Hyper-v server?
Why?: Because 1) I don't have storage on the SAN with enough space to accommodate the 1.2TB of VM data to export and I will need to export to a USB. Server hardware is HP DL380 G7 with USB 2... Will take forever!
2) Importing on the Cluster, same issue. Time.
3) Seeing as I don't have spare capacity on the SAN, I would have to remove the data partition on the affected raid volume once export is complete. If USB (or whatever...) drive I used fails, OR the import fails, I will be reduced to recovering VM and VHD's
from backup. More time.
Any feedback will be greatly appreciated!
Thanks!