{"id":3303,"date":"2011-10-11T10:54:20","date_gmt":"2011-10-11T18:54:20","guid":{"rendered":"https:\/\/www.zubairalexander.com\/stage\/?p=3303"},"modified":"2011-12-24T11:23:22","modified_gmt":"2011-12-24T19:23:22","slug":"difference-between-hyper-v-saved-state-and-a-snapshot","status":"publish","type":"post","link":"https:\/\/www.zubairalexander.com\/blog\/difference-between-hyper-v-saved-state-and-a-snapshot\/","title":{"rendered":"Difference Between Hyper-V Saved State and a Snapshot"},"content":{"rendered":"

When working with\u00a0Microsoft Hyper-V, it is helpful to understand the difference between the Saved State and a Snapshot. Here is a brief explanation of both.<\/p>\n

Snapshot<\/strong><\/p>\n

A snapshot can be taken whether the virtual machine (VM) is running or not. It is a point in time of the state of a VM. You can revert back to a previous point in time whenever there is a need. For example, if you plan to install a service pack, you can take a snapshot before you install the service pack and if things go wrong, you can revert to the point in time before you installed the service pack. It is similar to the System Restore concept in\u00a0Microsoft operating systems. A snapshot consists of three components:<\/p>\n

    \n
  1. A single xml file for the VM configuration. This includes all the settings that you configured for the VM, such as memory, number of processors, description of the VM, etc.<\/li>\n
  2. A memory save state file.<\/li>\n
  3. A difference disk, which is a file that ends with the extension .avhd. There will be a separate .avhd file for each snapshot.<\/li>\n<\/ol>\n

    Saved State<\/strong><\/p>\n

    A Saved state is a point in time of a running VM, however, unlike a Snapshot, a Saved state can only take place on a VM that is running. Also, a Saved state can be restored only once (as long as you have not applied a Snapshot since the system state was saved). This is different than\u00a0Snapshot because a Snapshot can\u00a0be restored multiple times. In fact, you can go back and forth between different Snapshots to the exact point in time when the Snapshots were taken.<\/p>\n

    Taking a Snapshot<\/strong><\/p>\n

    To take a Snapshot, simply right-click a VM in the Hyper-V console and select Snapshot. The VM may be running or shutdown.\u00a0You may also delete a Snapshot, whether the VM is running or not.<\/p>\n

    Saving the\u00a0State<\/strong><\/p>\n

    To save the system state, right-click the VM while it is running and select Save. Your VM will appear to be shutdown. To resume, you simply right-click the Saved VM and select Start.<\/p>\n

    As great as Snapshots are, keep in mind that according to Microsoft if you have more than three Snapshots for a VM, you may experience performance degradation. However, the degradation will depend on\u00a0the amount of\u00a0RAM and processors that are available and how you have configured the system resources.<\/p>\n

    \n

    Copyright \u00a92011 Zubair Alexander. All rights reserved.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

    When working with\u00a0Microsoft Hyper-V, it is helpful to understand the difference between the Saved State and a Snapshot. Here is a brief explanation of both. Snapshot A snapshot can be taken whether the virtual machine (VM) is running or not. It is a point in time of the state of a VM. You can revert […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[46,30],"tags":[],"class_list":["post-3303","post","type-post","status-publish","format-standard","hentry","category-virtualization","category-longhorn-server"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t