CLIENT AREACall Us 1-800-383-5193


Call Us 1-800-383-5193


Call Us 1-800-383-5193

Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Production checkpoint in Hyper-V 2016

by | Jan 5, 2021

Wondering how to set Production checkpoint in Hyper-V 2016? We can help you with it.

Here at Bobcares, we have seen several such Nagios-related queries as part of our Server Management Services for web hosts and online service providers.

Today, we will get into the details of the checkpoint in Hyper-V 2016


Checkpoint in Hyper-V 2016

Hyper-V checkpoints are mainly used to save the existing state of a virtual machine before any changes are made so that if any problem arises due to the changes, the VM can revert to its previous state.

There are two types of checkpoints: standard checkpoints and production checkpoints.

  • Production checkpoints are “point in time” images of a virtual machine. We can use it to restore later on in a way that is completely supported for all production workloads. We can do this by using backup technology inside the guest to create the checkpoint, rather than using saved state technology.
  • A standard checkpoint takes a snapshot of the state, data, and hardware configuration of a running virtual machine. But is not a full backup of the VM. However, if we need to recreate a specific state or condition of a running virtual machine then Standard checkpoints are useful.

When a VM checkpoint is created in Hyper-V 2016, by default, new Production Checkpoints are used.


Change checkpoints to production or standard checkpoint in Hyper-V 2016

Now let’s see how our Support Engineers change the checkpoints in Hyper-V.

  1. First, in Hyper-V Manager, we right-click the virtual machine and click Settings.
  2. Next, under the Management section, we select Checkpoints.
  3. Here we either select production checkpoints or standard checkpoints.
    In case, if we choose production checkpoints then we can also specify whether the host should take a standard checkpoint if a production checkpoint can’t be taken.
    production checkpoint in hyper-V 2016
  4. We can change the Checkpoint File Location section if we wish to store the checkpoint configuration files in a different place.
  5. Finally, we click Apply to save the changes. Once done, we click OK to close the dialog box.


We can switch the modes of Hyper-V checkpoints creation by running the below PowerShell commands:

Set-VM -Name Lon-SQL1 -CheckpointType Disabled
Set-VM -Name Lon-SQL1 -CheckpointType Standard
Set-VM -Name Lon-SQL1 -CheckpointType Production
Set-VM -Name Lon-SQL1 -CheckpointType ProductionOnly

A VM checkpoint is created as usual: in the Hyper-V console or in PowerShell.

CheckPoint-VM –Name Lon-SQL1

When creating a Production Checkpoint, in the Application log of the guest VM you can find the events showing the start and finish of creating the application consistent state with VSS.

After rollback to the Production Checkpoint created earlier, we must manually turn on the VM. Both the guest OS and the running application will consider that earlier they shut down correctly.

[Need any further assistance with Hyper-V checkpoints queries? – We are here to help you]



Today, we saw how our Support Engineers change the checkpoints in Hyper-V.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *