![]() ![]() This is especially the case since I'm going to start getting back into Windows Server Technical Preview and the Hyper-V features soon. Reclaiming that primary space is a good idea. And by holding on to these unused VMs, I've been effectively provisioning precious VMware vSphere and Microsoft Hyper-V primary datastore and volume space for something I may not use again. I like the idea of backing them up, as almost any backup technology will have some form of compression and deduplication, which will save some space. I've decided it's best to back these VMs up and then delete them. ![]() These two characteristics made me wonder if I really need to hold on to them any more. Secondly, I really don't have the infrastructure size to power them all on at once. First of all, I was holding on to these VMs "only if I'd need them" and based on the timestamps of the its last activity, it was usually quite awhile ago. Given that this is a large number of powered off VMs, a few interesting attributes come into play. This is a practice of mine in my home labs, but I was shocked to see how somewhat sloppy I've become with powered-off VMs outside of that setting. Approximately 35 percent of the environment's nearly 800 VMs were powered off. I recently took a look at one of the larger VMware vSphere and Microsoft Hyper-V environments I work with, and noticed that I had high number of powered-off VMs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |