It's really lame that the default Hyper-V manager doesn't include an automated clone process. So I got all excited when I found that System Center Virtual Machine Manager does and it's free through my MSDN subscription. I downloaded it, got ready to install it, only to have it error out and say I need to be joined to a domain. This seems to be an epic fail that I would need Active Directory to use it. Is there a way around this or are there other tools that integrate with Hyper-V that are just as good (or better) and free?
feedback
|
|
I too tried System Centre VMM and was underwhelmed, but that was more to do with it being disproportinate to my needs rather than because it is lacking as software. I run a cluster with 2 nodes, and an additional couple of servers, and to be honest I feel that VMM is overkill in this scenario. There's one thing I really do like about it though, the quick storage migration is fantastic and worked every time, and for that reason alone, using VMM saved me a lot of sweat when I reconfigured my storage. I'm not sure what exactly you mean by cloning. If it is physical to virtual then I've no experience, but if it's virtual to virtual i.e. fast deployment and building multipile versions of the same VM for testing, customer provision, ans so on, then I have just started using a product that I am totally blown away by, it's name is Virsto and it is sold primarily as a storage optimizer, but it has a brilliant cloning and snapshot feature. After you've got it set up, it's literally a couple of clicks to clone a disk and create a new VM. It is beyond words, honestly, it is that good. The other nice thing about Virsto is that you can add clones without carving chunks out of your storage capacity. 10 VMs take up as much room as 1 VM + any variations between them at bit level. I'm in early stages of testing this, and it still costs (it is not 'free' like VMM on MSDN) but my initial impression is that it just works. But I think Virsto's' biggest challenge is going to be marketing, because Enterprises are only just waking up to Hyper V, and smaller concerns are going to be looking for cheap fixes. But for virtual cloning it saves bags of time. Otherwise, before Virsto I just used sysprep and copied the files, but this takes time and is fiddly. | |||||||||||
feedback
|
|
SCVMM is a bit overkill for a 2 node cluster, but requiring AD for security make perfect sense. It's pretty quick to "clone" a VM by shutting it down, copying the VHD, and creating a new VM pointing to the copied VHD. It does require configuring all the VM hardware, but after you do it a could times you'll be able to configure a VM in less than a minute. On a side note, I'd never run a cluster on a full server install. There's a lot of overhead needlessly added and Hyper-V Server 2008 R2 is both free and supports clusters. | |||||||||||||
feedback
|
|
Chris, Virsto is (much) more than just differencing disks. One of its features is in fact can be interpreted as a differencing VHD but the devil is in the details. Differencing disks are Ok for a quick prototype, however with any kind of a meaningful IO load diff disks fell pretty quickly. In a cluster environment (CSV) diff disks are basically unusable. Virsto provides scalable cluster virtual disks, thinly provisioned, with an ability to do instant snapshotting and cloning with no performance penalty. You can out 3 times as many VMs on the same set of storage devices and still have a better performance compared to either fixed VHDs. | |||
|
feedback
|