Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Hyper-V / Production Checkpoint in Hyper-V 2016

September 28, 2017 Hyper-VWindows Server 2016

Production Checkpoint in Hyper-V 2016

The Hyper-V version available in Windows Server 2016 and Windows 10 has got a new feature called Production Checkpoints. Checkpoints (previously known as snapshots) appeared in Hyper-V in Windows Server 2008 and represented a mechanism for saving the current state of the virtual machine (saving the states of a disk, memory, processors and devices). If necessary, an administrator can roll back a VM to its state at the moment when this point has been created. This type of a checkpoint doesn’t depend on the guest VM, which doesn’t know anything about the checkpoint. The main drawback of checkpoints is their inability to provide consistency of applications running inside the VM (SQL Server database, Active Directory, Exchange, etc.). Thus, Microsoft recommends to use standard Hyper-V production checkpoints (we’ll call them Standard Checkpoints) only in test or lab environments.

Due to their integration with the guest OS using VSS (in Windows) or fsfreeze (in Linux), Production Checkpoints in Windows Server 2016 allow to get a consistent state of a virtual machine (obviously, if an application supports shadow copying via VSS).

Note. When using Production Checkpoints instead of XML files stored together with the VM, two new types of binary files are used: .vmcx – configuration data, .vmrs – state data.

When a VM checkpoint is created in Hyper-V 2016, new Production Checkpoints are used by default, and if they are not supported on any reasons, Standard Checkpoints are used.

The checkpoint type is set in Hyper-V Manager in the Checkpoints section of the Settings tab.

hyper v 2016 - production checkpoints

You can switch the modes of Hyper-V checkpoints creation using the following 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

Note. Production Checkpoint is supported for a VM with the virtual equipment version 6.0 or higher.

A VM checkpoint is created as usual: in the Hyper-V console or in PowerShell.
create checkpoint for selecte hyper-v vm

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, you must manually turn on the VM. Both the guest OS and the running application will consider that earlier they shut down correctly.

However, you shouldn’t forget that Hyper-V checkpoints are not the full-featured backup tool. Their scope is short-term tasks (testing releases, updates, changes, etc.).

0 comment
0
Facebook Twitter Google + Pinterest
previous post
Fix: Server Stuck on “Preparing to Configure Windows”
next post
Fix: Windows Cannot Connect to the Printer Error 0x00000057

Related Reading

The Disk is Offline Because of Policy Set...

December 12, 2019

How to Backup Hyper-V Virtual Machines?

December 10, 2019

How to Change a Network Location from Public...

December 9, 2019

Configuring Storage Replica on Windows Server 2016

December 4, 2019

How to Delete Old User Profiles Using GPO...

November 19, 2019

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Follow us

woshub.com

Recent Posts

  • VMWare: How to Find VMs by IP or MAC Address?

    December 13, 2019
  • The Disk is Offline Because of Policy Set by an Administrator

    December 12, 2019
  • How to Backup Hyper-V Virtual Machines?

    December 10, 2019
  • How to Change a Network Location from Public to Private on Windows 10/Windows Server 2016?

    December 9, 2019
  • Configuring Storage Replica on Windows Server 2016

    December 4, 2019
  • Windows 10 Install Error 0x80300024

    December 2, 2019
  • Running PowerShell Script (*.PS1) as a Windows Service

    November 27, 2019
  • Creating Multiple Partitions on a USB Drive in Windows 10

    November 26, 2019
  • VMWare vSphere: Failed to Upload Files to Datastore

    November 21, 2019
  • How to Delete Old User Profiles Using GPO and PowerShell?

    November 19, 2019
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Stop a Hung Virtual Machine on Hyper-V 2016
  • Hyper-V PowerShell Direct in Windows Server 2016
  • VHD Set: Shared Virtual Disks on Hyper-V 2016
  • How to Install Hyper-V Role in Windows 10 VM under VMWare ESXi
  • Configuring Hyper-V Live Migration without Failover Clustering
  • Using Differencing Disks in Hyper-V for Quick VM Deployment
  • Detecting Memory Overcommitment in the Guest OS
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top