Skip to main content

Hyper-V Checkpoints: Why, When and How to Use Them

Hyper-V Checkpoints: Why, When and How to Use Them


HyperVCeckpoints-min
Before making changes in Hyper-V, whether it involves software configuration changes or a new software update, it's a good idea to first create a Hyper-V checkpoint.
Hyper-V checkpoint follows the same idea of the more well-known Microsoft Windows restore point that many Windows users have utilized in the past before adding new applications or making other system changes to their machines. Hyper-V checkpoints allow IT administrators to easily save the existing state of a virtual machine before any changes are made so that if a problem crops up due to the changes, the VM can revert to its previous state.
That's a very useful feature for VM administrators, since new configuration changes can always potentially bring new challenges to enterprise IT systems.
Two types of checkpoints are available for use in Windows 10 Hyper-V, including standard checkpoints and production checkpoints.
A standard checkpoint takes a snapshot of the virtual machine and virtual machine memory state, but is not a full backup of the VM. Previously known as Hyper-V Snapshots prior to Windows 10, a standard checkpoint can cause consistency issues with systems that replicate data between different nodes such as Active Directory.
A production checkpoint does allow IT administrators to gain increased protection for systems by creating a data-consistent backup of the VM using Volume Shadow Copy Service or File System Freeze on a Linux VM. A snapshot of the virtual machine memory state is not taken when using a production checkpoint.
Production checkpoints do not include information about running applications, while standard checkpoints do capture the state of current applications.
Administrators can select production or standard checkpoint options using either Hyper-V manager or PowerShell, but the production checkpoint option is usually selected by default.
Checkpoints can later be deleted when they are no longer needed after proper system operations have been verified.
The availability of checkpoints for Hyper-V arrived with Windows Server and Windows 10. The feature uses backup technology inside the guest to create the checkpoint, instead of using saved state technology.
Standard checkpoints capture the state, data and hardware configuration of a running virtual machine, and are intended for use in development and test scenarios. Standard checkpoints can also be useful to administrators who need to recreate a specific state or condition of a running virtual machine to troubleshoot a problem.
Hyper-V checkpoints are an excellent tool for enterprise IT administrators to keep in their toolbox for preventing problems when system or software changes are being made.
Checkpoints add a great range of use cases and knowing which option to rely on in different scenarios will help you ensure your VMs can be quickly reverted to a saved state technology in the event of corruption or another undesirable state.

Comments

Popular posts from this blog

[RAID] SWITCH FROM AHCI TO RAID WITH INTEL C600 CONTROLLER

I personally have used other ways to do this. Manipulating some registry settings in combination with a safe boot before booting normally does the trick as well. This works with both SATA SSD and M.2 NVMe drives and it enables relatively fast switching between back and forth between AHCI and RAID. I have described this method below.  I have also tried the same process used to switch from RAD to AHCI and that works as well. Switch to safe boot Reboot into BIOS Change from AHCI to RAID in the BIOS Boot into safe mode Turn off safe mode and reboot normally again Nothing else and that also did the trick, just like with moving from RAID to AHCI.  So the link above and my step by step below is here for completeness. You have options in case one of them doesn’t work! Step by step AHCI to RAID registry method This procedure I describe below works on Windows 10 1803/1809 and has been tested on Dell Latitude E6220 an XPS 13 9360. Editing the registry is...

[Hyper-V] - Lỗi không boot vào được sau khi convert máy vật lý sang máy ảo

XỬ LÝ LỖI KHÔNG BOOT ĐƯỢC VÀO MÁY ẢO SAU KHI CONVERT TỪ MÁY VẬT LÝ BẰNG DISK2VHD Sau khi convert server vật lý sang file VHD để import vào Hyper thì khi start máy ảo lên màn hình máy ảo chỉ nhấp nháy con trỏ chuột trên màn hình đen (blinking cursor) NGUYÊN NHÂN Do máy vật lý sử dụng ổ đĩa cài OS được format theo chuẩn GPT (thay vì MBR như truyền thống, tham khảo GPT và MBR ) XỬ LÝ Bước 1: chuyển ổ GPT thành MBR Copy file VHD của ổ đĩa chứa OS về 1 máy tính Windows 8 trở lên Trên máy Windows 8+ click phải chuột lên file VHD vừa copy, chọn lệnh Mount . Lúc này dùng 1 phần mềm miễn phí (vd: Mini Partition Wizard ) để convert ổ đĩa vừa mount từ GPT  -> MBR Sau đó Delete phần Partition dư ra ở phần đầu ổ đĩa được mount (khoảng vài trăm MB) Set " Active " cho ổ đĩa này để là ổ đĩa boot OS Nhấn Apply để phần mềm thực thi tác vụ Sau khi phần mềm làm xong, tắt phần mềm Mini Partition Wizard, vào My Computer chọn eject ổ đĩa đang mount . Copy file VHD vừa đư...

LỖI "The provided partition "Migration...." is not a valid Migration mailbox"

  Solution for a valid Migration mailbox could not be found for this organization To address this issue, we will: Delete Migration mailbox in Active Directory Users and Computers Recreate Migration mailbox with /PrepareAD command Enable Migration mailbox with Exchange Management Shell 1. Delete Migration mailbox in Active Directory Users and Computers We do see the mailbox in ADUC, let’s remove it. If you don’t see it, search for it. It might be in a different container than the default container  Users . We can always verify in Exchange Management Shell if the Migration mailbox is present. If it shows up in the output, it means that it’s present and enabled. The output should be empty. [PS] C:\> Set - ADServerSettings - ViewEntireForest $true ; Get - Mailbox - Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" - Arbitration | Format-Table Name , ServerName , Database , AdminDisplayVersion , ProhibitSendQuota Copy 2. Recreate Migration mailbox with /Prepare...