How to test the creation of Production Checkpoints in Hyper-V 2016/2019

KB ID: 3137
Product: Veeam Backup & Replication
Published: 2020-03-31
Last Modified: 2022-04-08
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents how to force Hyper-V 2016 or newer to create a Production Checkpoint

Cause

Forcing Hyper-V to create a Checkpoint in ProductionOnly mode is used as an isolation step when troubleshooting a Veeam job that fails to create a Recovery Checkpoint with Application-Aware Processing or Hyper-V guest quiescence enabled.
Failed to create VM recovery checkpoint (mode: Veeam application-aware processing)

A Hyper-V Production Checkpoint and the Recovery Checkpoint requested by a job using Application-Aware Processing or Hyper-V guest quiescence both trigger VSS activity within the VM's guest OS. For this reason, if both the job (with those settings enabled) and the Production Checkpoint fail, the issue is environmental.

Note: Disabling both Application-Aware Processing and Hyper-V guest quiescence will remove the interaction with Guest VSS and may allow the Veeam job to complete. If the job completes with these settings disabled, this does not resolve the underlying issue; it only bypasses the VSS issue and further demonstrates that there is an underlying environmental problem.

Solution

It is imperative that all steps be followed precisely to ensure the test results are valid.

Create Production Checkpoint using Hyper-V Manager

The steps below are to be performed on the VM that Veeam is failing to create a Recovery Checkpoint for.

  1. Connect Hyper-V manager to the host where the VM is located.
  2. Right-click the VM and select Settings
settings screenshot
  1. In the Checkpoints section, ensure the option "Create standard checkpoints if the guest does not support creation of production checkpoints." is unchecked (disabled).

    If this is not disabled, the test results will be invalid.
You must make sure failover to standard checkpoint is disabled or else the test is invalid.
Wrong Setting
WRONG SETTING
Correct Setting
CORRECT SETTING
  1. Validate Checkpoints are set to Production-Only, and then click Ok to save the settings.
  2. Right-click the VM and select Checkpoint
Create checkpoint

If you were asked to perform this Isolation Test as part of a Veeam Support case, report the results on the case.

 

If Hyper-V failed to create a Checkpoint in ProductionOnly mode, initial troubleshooting steps are at the bottom of this article.

Snapshot Removal

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

You can select the VM and view all checkpoints under the Checkpoints section. Right-click on the checkpoint and select the Delete Checkpoint option.

Create Production Checkpoint using PowerShell

  1. Start PowerShell in administrative mode on the host for the necessary machine.
  2. Set the type of checkpoint created to Production Only:
Set-VM %vm_name% -CheckpointType ProductionOnly
  1. 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!
The following PowerShell command will remove all existing checkpoints from the VM.
Get-VM vm_name | Get-VMSnapshot | Remove-VMSnapshot

More Information

The following troubleshooting steps are provided as a courtesy. Veeam Support recommends that you contact Microsoft Support for assistance if the Hyper-V environment cannot create a Production Checkpoint in ProductionOnly mode.

If the Production Checkpoint process immediately fails with "Production checkpoints cannot be created.",  check the following:

  1. Within the Guest OS of the VM in question:
    • Volume Shadow Copy is set to Manual startup type.
    • Hyper-V Volume Shadow Copy Requestor service is set to Manual startup type.
    • Hyper-V Volume Shadow Copy Requestor service is Running.
  2. On the Hyper-V host where the VM is located:
    • Check the VSS Integration status using the following PowerShell command:
Get-VMIntegrationService -VMname "vmname"

If VSS is listed as "Lost Communication" (see example below), make sure the Hyper-V Volume Shadow Copy Requestor service is "Running". If it is already running, restart it and recheck the integration state. If the VSS Status changes to OK, perform the ProductionOnly Checkpoint creation test again. If the test succeeds, remove the checkpoint, and run the Backup job.

 

vss lost communication
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.