Jan 15
Aaron Sweemer over at Virtual Insanity had an interesting post from a couple of weeks ago about the disk storage savings from using the new VMware View Composer. Prior to Composer if you wanted to create 100 VMs and the individual VM was Windows XP with a 10 GB disk then you’d use up (100 * 10 = 1,000 GB) of disk space. Now with VMware View Composer you’d only use up 10 GB for the original VM and a small differential of space for each additional VM. How big is the differential? Well, it will vary depending on how much is changing. For a good look at a real use case finish reading the article at the source.
January 15th, 2009 at 12:43 pm
[...] 15, 2009 Disk Savings from VMware View Composer: [...]
January 17th, 2009 at 1:31 pm
Don't forget to install in OLTP mode and secure the database wich contain all informations about the clones !
January 17th, 2009 at 2:59 pm
I've seen posts saying that this savings is not entirely true for long with VMWare View. That because Windows does not readily overwrite previously used blocks, in the name of providing you the opportunity to undelete if needed, it continues writing new blocks, which means disk sizes keep growing.
This means things could balloon pretty quickly in the case of one or more people downloading a large file on one of the VMs, say an ISO image, and then deleting it.
January 17th, 2009 at 7:14 pm
You mean like if system restore is running? IIRC that's one of the first things they tell you to turn off when making a VDM/View image. That would account for that behavior, that and maybe unchecked browser and temp caching.
January 17th, 2009 at 8:31 pm
Don't forget to install in OLTP mode and secure the database wich contain all informations about the clones !
January 17th, 2009 at 9:59 pm
I've seen posts saying that this savings is not entirely true for long with VMWare View. That because Windows does not readily overwrite previously used blocks, in the name of providing you the opportunity to undelete if needed, it continues writing new blocks, which means disk sizes keep growing.
This means things could balloon pretty quickly in the case of one or more people downloading a large file on one of the VMs, say an ISO image, and then deleting it.
January 18th, 2009 at 2:14 am
You mean like if system restore is running? IIRC that's one of the first things they tell you to turn off when making a VDM/View image. That would account for that behavior, that and maybe unchecked browser and temp caching.