It’s fine to use snapshots on test or dev VMs, but don’t use them on production VMs. VM snapshots take up significant space, so you should limit yourself to 2 or 3 of them.
Click Since the Patch 2 snapshot does not have the machine’s memory, you will have to start the VM manually. The snapshot manager screen will indicate where you are within the snapshot tree. Note that you’ll get a message saying that the “current state of the virtual machine will be lost unless it is saved in a snapshot.” This means that if you have made any changes to the VM and have not saved them by creating a snapshot, your work will be lost. To revert to a snapshot, from the snapshot manager, choose one of the snapshots (for example Patch 2) and click Revert To.ģ. If we revert to a snapshot with a green icon, the VM will be in running state.ġ. The figure below shows several snapshots to choose from. If you check this box and the VM is running when you take a snapshot, the icon of the snapshot will be green.Ĥ. If you check the “Snapshot the virtual machine’s memory” option, the snapshot will also record the VM’s memory. It is recommended to include a detailed description of what has been done to the VM or how the VM is configured.ģ. In the pop-up window, enter a name and description for the snapshot. Alternatively, you can select VM > Actions > Snapshots > Take snapshot.Ģ. Access the VMware vSphere snapshot manager by right-clicking on a VM, and then click Create Snapshot. This is supported in vSphere 5.0 and later.ġ.