Skip to main content

Some notes about Hyper-V Snapshots

Snapshots allow you to capture the current state of a VM, and return it to that point-in-time at your convenience. Snapshots are the closest thing that we have to the Restore Points we had in Windows XP. There are a few things that you need to know about snapshots.
  • They do not affect a running virtual machine. If a snapshot is taken and a change to the state of the VMs memory is made, Hyper-V will intercept that change and hold it until the snapshot is complete.
  • The virtual machine cannot be in a paused state.
  • If you take a snapshot while logged in, when you return to that snapshot, it will be right were you took it. This includes being logged in and applications running.


Here is the snapshot process:

1. Pauses the virtual machine.

2. Creates differencing disks associated with all VHDs configured in the virtual machine, and then associates them with the virtual machine.

3. Makes a copy of the virtual machine’s configuration file.

4. Resumes the running of the virtual machine.

5. Saves the contents of the virtual machine to disk.


The snapshot will create some files and store them in the Virtual Machines folder

.xml: virtual machine configuration files

.vsv: virtual machine saved state files

.bin: virtual machine memory contents

.avhd: snapshot differencing disks

clip_image001
Above is a looking inside a virtual machines folder. Notice the many .AVHD files. Each one of these is for a single snapshot.

clip_image002
Opening up the snapshots folder, we seethe .xml files that hold the configurations from each of the snapshots. If we open up one of the folders, notice the highlighted on above is a GUID that matches the last .xml file, we see the files containing the memory state and the saved state of the VM snapshot.

clip_image003

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.