Some time ago, I published articles on setting up a home lab using a PC running ESXi and Workstation. We all know that nested virtualization is not an ESXi-only feature; Microsoft Hyper-V also enables us to run VMs inside its VMs. Microsoft’s implementation of this technology is a bit different, but it exists. And, considering that VMware and Microsoft have been competing for a long time, it’s interesting to see what each has to offer for this type of virtualization. In this post, I examine how easy it is to configure a nested virtualization layer inside Hyper-V and vSphere VMs and discuss peculiarities of this process in both environments.
Lately, I often face people who prefer using snapshots, wrongly thinking that they can serve as an alternative to a proper backup infrastructure. This comes from a misunderstanding of snapshots’ real functions. So, I’ve decided to sort things out in this post and describe some basic operations you can do with snapshots in VMware and Hyper-V environments.
The term “snapshot” refers to the absolute copy of the particular VM’s state that allows you to roll back to it whenever you want. You can always take a snapshot of the VM, be it running or switched off. Though, if you capture a running VM, its disk activity gets suspended (for a matter of seconds but still…).
So, what’s the main point of taking snapshots?