Page 1 of 1

Snapshots vs. Virtual Machines

Posted: 14. Jul 2010, 11:14
by kna
Hi,

I've read a lot about Snapshots and am still uncertain as to the best way to go about achieving my scenario. I want to have a Standard OS build which contains some software and then build up several alternate versions of this to use for testing. As an example:

Vanilla Windows XP Build + Remote Admin Software
Vanilla Windows XP Build + Remote Admin Software + Cisco VPN Client
Vanilla Windows XP Build + Remote Admin Software + SecuRemote Client
Vanilla Windows XP Build + Remote Admin Software + Nortel VPN Client

I did have a grand plan of creating the initial build and then making Snapshots for all the additional clients. (Reverting back and building it with the next client, snapshotting again). I also want to be able to 'reset' any one of these builds if they become corrupted in anyway (either from a Virus, or simply too much messing about).

However, I'm a bit confused when it comes to adding a new piece of software to the build, such as an updated copy of VNC for example. Is this a situation where I would be better off with 4 VM's instead, and just update them all one by one, or can it work using the snapshot method. If so, how do I update a snapshot?

Sorry if this is clearly explained anywhere, all I seemed to find were 2-3 year old documents which tended to veer away from Snapshots for similar concepts.

Cheers.

Re: Snapshots vs. Virtual Machines

Posted: 14. Jul 2010, 18:49
by mpack
If your question is, "can I install an update in just the base VDI and let all the snapshot children inherit the update that way"? The answer is no, as I assume you suspected. Each snapshot child would have to be updated separately.

Updates are equally (in)convenient to apply whether you use snapshots or clones (which you call separate VMs). But, I prefer clones for other reasons, mainly better reliability.