1-800-691-1991 | 9am - 8pm ET

Creating a Production Checkpoint in Hyper-V 2016\2019


You need to create a production checkpoint for the 2016 Hyper-V VM.


Veeam uses the production checkpoint as a basis for application-aware processing on Hyper-V 2016. In order to test this functionality, it may be required to create the production checkpoint manually.


GUI method
  1. Go to the Hyper-V manager on the host where your VM is deployed.
  2. Right-click the VM and select "Settings".
  3. Uncheck the box "Create standard checkpoints if it's not possible to create a production checkpoint" and save settings.User-added image
  4. Right-click the VM and select "Checkpoint".
PowerShell method
  1. Start PowerShell in administrative mode on the host for the necessary machine.
  2. Set the type of checkpoint created to production:
    Set-VM %vm_name% -CheckpointType ProductionOnly
  3. Create a checkpoint:
    Checkpoint-VM %vm_name%

NOTE: Make sure to remove the checkpoint after the required tests. Active checkpoints may lead to a lack of free space on production datastores!
From GUI:

You can select the VM and view all checkpoints under "Checkpoints" section. Right-click over the desired checkpoint reveals the "Delete Checkpoint" button.

From PowerShell:

Get-VM vm_name | Get-VMSnapshot | Remove-VMSnapshot

NOTE: This action will remove all existing checkpoints from the VM.


Veeam Backup & Replication
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later