Hyper-V 2012 R2 to Hyper-V 8.1
HI,
Just for the sake or doing testing or implementing crash recovery, i have set the following & it is not working.
It does not make sense to me as I can do the same tests using VMware and tests are successful.
Here is what I have done.
I have created some Hyper V's on Windows Server 2012 R2's.
Now back to 8.1, I am trying to import those VM's. After clicking the Import Virtual Machine, & pointing to the correct location, the vm import is unable to see the vhdx file extension!
What the! Why cannot I import some vhdx that I clearly visible from the file location but Hyper-V cannot see them?
Thanks
Just for the sake or doing testing or implementing crash recovery, i have set the following & it is not working.
It does not make sense to me as I can do the same tests using VMware and tests are successful.
Here is what I have done.
I have created some Hyper V's on Windows Server 2012 R2's.
Now back to 8.1, I am trying to import those VM's. After clicking the Import Virtual Machine, & pointing to the correct location, the vm import is unable to see the vhdx file extension!
What the! Why cannot I import some vhdx that I clearly visible from the file location but Hyper-V cannot see them?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Casey Weaver
Just as a side note, did you actually export those VM's from Hyper-V 2012? You cannot just attach Hyper-V to another host's file set sadly. If export cannot be done (due to a failure situation) then you must select to the use the disk and rebuild the vm around that. As you've found out.
ASKER
No I didn't export them on purpose. I am just testing some disaster solution & hyper v backup.
It does not make sense to me to export for backup solution. Export is good for planning, but cannot plan when a disaster will happen
It does not make sense to me to export for backup solution. Export is good for planning, but cannot plan when a disaster will happen
Yes I agree with you 100%, that's why we tested it, and it is certainly one of the most glaring issues with Hyper-V. I highly recommend that those running Hyper-V either have full system backups (one click bare metal restore systems), a fail over cluster with centralized storage, or a replica setup.