How would you migrate from VMWare to HyperV?
-
in this case a V2V tool.
-
@scottalanmiller said:
P2V tools would be ideal, far better than a traditional backup -> restore operation.
Which tools, etc, are things I am inquiring about. I know some methods. I have checked into others. But I would assume that the user base here can give me hard examples.
I have never had a client in the position to migrate V2V at this point. P2V I have done before.
-
@Dashrender said:
in this case a V2V tool.
Those generally don't exist. You actually use P2V to do an "any to virtual" migration.
-
@JaredBusch said:
@scottalanmiller said:
P2V tools would be ideal, far better than a traditional backup -> restore operation.
Which tools, etc, are things I am inquiring about. I know some methods. I have checked into others. But I would assume that the user base here can give me hard examples.
I have never had a client in the position to migrate V2V at this point. P2V I have done before.
Not sure what P2V supports HyperV.
-
Some tools like Unitrends will do a backup and restore to disparate "hardware" which should work for moving between environments.
-
I've don the conversion a couple of times ... from VMWare to Hyper-V... I recommend Starwind. They have a free V2V converter tool that will allow you to switch the file formats. It works wonders... just set your email up when you register to go to a throw-away account...
-
@milnesy said:
I've don the conversion a couple of times ... from VMWare to Hyper-V... I recommend Starwind. They have a free V2V converter tool that will allow you to switch the file formats. It works wonders... just set your email up when you register to go to a throw-away account...
Awesome, I had no idea that they had that.
-
-
I've not tried this in a VM, but maybe?
https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx -
@NetworkNerd the p2v for this is nice... just remember to check off a box if you're looking to use hyper-v on 2012... The downside though is that you might get a bloated VM because you can't move some of the blocks from the end of the vm to the front. Had that happen to me on one drive that was a 160gb vm using only 40gb. used the tool and was left with a 120gb vm... turned out that there were 'unmovable files' at the end of the vm image...
