Back up every volume containing Hyper-V configuration, checkpoint, and virtual-disk files with Windows Server Backup; backing up only the host’s system volume can leave the VMs incomplete and unable to start.
1. Inventory the VM storage locations
Run PowerShell as Administrator to record each VM’s configuration, checkpoint, and virtual-disk locations:
Get-VM | Select-Object Name, Path, SnapshotFileLocation
Get-VM | ForEach-Object {
Get-VMHardDiskDrive -VMName $_.Name |
Select-Object VMName, ControllerType, ControllerNumber,
ControllerLocation, Path
}
Build a list of all affected volumes—for example:
-
C:— default Hyper-V metadata, includingC:\ProgramData\Microsoft\Windows\Hyper-V -
D:— VM configuration or checkpoint files -
E:— VHD/VHDX files
All volumes hosting these files must be included in the same backup. Microsoft specifically requires the volume containing InitialStore.xml, VM configuration files, and every VM disk volume.^1^
2. Configure the daily backup
Use a separate backup disk or destination with enough capacity for all selected volumes. If Windows Server Backup is not installed, add the Windows Server Backup feature first.
Open Command Prompt as Administrator. Scheduled backups require membership in Administrators or Backup Operators.^2^
For example, to back up C:, D:, and E: every day at 23:00 to backup volume H::
wbadmin enable backup -addtarget:H: -include:C:,D:,E: -schedule:23:00 -vssFull -quiet
Replace the drive letters with those found during the inventory.
Important considerations:
- Do not use a VM storage volume as the backup destination.
- Selecting an entire disk as the target can format that disk and permanently erase its existing contents.^2^
- If another backup product also protects these volumes, use
-vssCopyinstead of-vssFull; a VSS full backup can affect the other product’s incremental or differential backup history.^2^ - For a network share, configure the destination through the Windows Server Backup interface rather than placing a password in a command or script. Repeated backups of the same server to the same remote folder overwrite the previous backup, so use distinct subfolders when multiple versions are required.^2^
3. Run and validate the first backup
Do not wait for the first scheduled execution. Start an initial backup—for example:
wbadmin start backup -backuptarget:H: -include:C:,D:,E:
The full-server wbadmin syntax supports specifying the destination and included volumes.^3^
After completion:
- Open Windows Server Backup.
- Confirm that Last backup status reports Successful.
- Confirm that all intended source volumes are listed.
- Perform a test recovery to an alternate location before relying on the schedule.
VMs without working Integration Services, or guests that do not support VSS, may briefly enter a saved state while the snapshot is created. VMs using dynamic disks—meaning guest dynamic disks, not dynamically expanding VHDX files—must be backed up offline. Windows Server Backup does not support this Hyper-V backup method on Cluster Shared Volumes.^1^
4. Restore all VMs
Windows Server Backup restores the Hyper-V application set rather than selecting an individual VM:
- Open Windows Server Backup.
- Select Actions → Recover.
- Select the server and backup date/time.
- Select Applications as the recovery type.
- Select Hyper-V.
- Select the recovery location.
- Select Recover.
All volumes hosting files for the VM are restored; this built-in recovery process does not restore an individual VM independently.^1^
If rebuilding the host first, install Windows Server 2019 and the Hyper-V role, recreate the required virtual switches, and then perform the Hyper-V application recovery. Restored VM networking reconnects when the original virtual switches still exist.^4^
If Hyper-V is missing under Applications
Apply this only if the recovery wizard does not offer Hyper-V. This modifies the registry, so export the affected key before proceeding.
- Open
regedit. - Go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion - Create this key hierarchy:
WindowsServerBackup\Application Support\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} - Under the GUID key, create a String Value named:
Application Identifier - Set its value to:
Hyper-V - Close Registry Editor and run another backup.
These values register the Hyper-V VSS writer with Windows Server Backup.^1^
If a VM with multiple checkpoints fails to restore
- In Hyper-V Manager, delete the VM entry that failed to restore.
- Run Recover again, selecting Files and folders.
- Restore its checkpoint directory; the default is
C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots. - Run recovery a second time using Applications → Hyper-V.^1^
References