I am attempting to convert a .vmdk and add it onto our Hyper-V storage cluster, which symbolically points to our SAN. I am at the last step of the process where I can finalize the conversion process but it is telling me there is not enough space on the disk to complete the conversion. I am trying to place the disk on the same storage cluster that all our other Hyper-V VMs are on, which has many TBs of free space available. The cluster storage is a symbolic link back to the SAN but the V2V converter doesn't see it that way. It only sees that there is about 100GB left on the C: and will not let me proceed with the conversion. We cannot be the first group to try to restore to the standard "Cluster Storage" location that symbolically points back to a SAN, right?
After thinking about this process more, I have a question. Do I need to complete the conversion process on the same platform that I plan to run the .vmdk on? Or can I convert the disk on any platform and then move it over to the Hyper-V host?
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software