Backup of the entire Hyper-V host

Hakim Fahadi 40 Reputation points
2026-11-17T11:21:54.5233333+00:00

Need help with backing up the entire hyper-v host. Guided steps would be more helpful

Windows for business | Windows 365 Enterprise
0 comments No comments

3 answers

Sort by: Oldest
  1. AI answer

    2026-11-17T11:25:15.9733333+00:00

    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, including C:\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 -vssCopy instead 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:

    1. Open Windows Server Backup.
    2. Confirm that Last backup status reports Successful.
    3. Confirm that all intended source volumes are listed.
    4. 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:

    1. Open Windows Server Backup.
    2. Select Actions → Recover.
    3. Select the server and backup date/time.
    4. Select Applications as the recovery type.
    5. Select Hyper-V.
    6. Select the recovery location.
    7. 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.

    1. Open regedit.
    2. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    3. Create this key hierarchy: WindowsServerBackup\Application Support\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
    4. Under the GUID key, create a String Value named: Application Identifier
    5. Set its value to: Hyper-V
    6. 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

    1. In Hyper-V Manager, delete the VM entry that failed to restore.
    2. Run Recover again, selecting Files and folders.
    3. Restore its checkpoint directory; the default is C:\ProgramData\Microsoft\Windows\Hyper-V\Snapshots.
    4. Run recovery a second time using Applications → Hyper-V.^1^

    References

    1. How to back up Hyper-V virtual machines from the parent partition on a Windows Server computer by using Windows Server Backup
    2. wbadmin enable backup
    3. Active Directory Forest Recovery - Back up a full server
    4. Backing up and restoring virtual machines
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Ronald Sabiiti 2,000 Reputation points Independent Advisor
    2026-11-17T12:14:08.8166667+00:00

    Hi Fahadi,

    For a complete Hyper-V host backup, I recommend using Windows Server Backup to perform a bare-metal recovery backup.

    Please follow these steps:

    • Install the Windows Server Backup feature through Server Manager or PowerShell.
    • Open Windows Server Backup and select Backup Once or Backup Schedule.
    • Choose Full Server to include the operating system, system state, Hyper-V configuration, and other required volumes.
    • Select a separate backup destination, preferably an external disk or dedicated backup storage.
    • After the backup completes, verify its status and periodically test the recovery process.

    For reference:

    Hope this helps!

    Ronald

    Was this answer helpful?

    0 comments No comments

  3. Marcin Policht 113.3K Reputation points MVP Volunteer Moderator
    2026-11-17T12:57:15.7033333+00:00

    Assuming you intend to use native Windows Server capabilities, you might want to consider Windows Server Backup (WSB) to protect the entire Hyper-V host, including its operating system and virtual machines. No third-party backup software is required.

    Start by installing the Windows Server Backup feature (you can do this by using PowerShell):

    Install-WindowsFeature Windows-Server-Backup
    

    You can then open the Windows Server Backup console by running wbadmin.msc. Select Backup Schedule to configure recurring backups. For a complete host backup, select Full server. This includes the volumes required for bare-metal recovery and the data stored on the selected server volumes. Alternatively, you can select Custom and explicitly include the volumes containing the Hyper-V virtual machine configuration files and VHDX files, along with the critical volumes required for recovery. I would use Full server unless you have a specific reason to exclude data.

    Configure the backup destination on a separate physical disk or a network share. Ideally, use dedicated backup storage that is not dependent on the Hyper-V host itself. A separate internal disk provides some protection against operating system or system-disk failure, but it does not protect against complete server failure. A network share or external disk provides better separation. Keep in mind that Windows Server Backup has different retention behavior depending on whether you use a dedicated backup disk or a network share.

    Windows Server Backup integrates with Hyper-V through the Volume Shadow Copy Service (VSS). This allows it to back up running virtual machines without requiring you to shut them down, provided the guest operating systems and integration services support the necessary VSS operations. Application-aware consistency also depends on the guest operating system and its VSS writers. You should verify that the Hyper-V VSS writer is functioning correctly before relying on the backups.

    For additional protection, I would periodically export the Hyper-V configuration information. For example, Get-VM | Export-Clixml C:\Backup\VMInventory.xml captures the VM inventory, and Get-VMSwitch | Export-Clixml C:\Backup\VMSwitches.xml captures virtual switch configuration. You should also preserve information about VLAN assignments, VM storage locations, virtual network adapters, and other host-specific settings. These exports are supplementary documentation rather than substitutes for the actual backup.

    For recovery, Windows Server installation media provides access to the recovery environment. You can use System Image Recovery / Bare Metal Recovery to restore the host from a compatible Windows Server Backup image. This is particularly important if the physical server fails or the operating system becomes unrecoverable. You should test this procedure rather than assume that a successful backup job guarantees a successful recovery.

    You can also use Windows Server Backup to restore individual volumes or files, while Hyper-V provides the ability to import previously exported virtual machines. This gives you several recovery options without needing to restore the entire physical server every time an individual VM has a problem.

    Schedule a daily Full Server backup to dedicated backup storage, retain an additional copy on separate storage or offline media, and periodically test both individual VM restoration and bare-metal recovery.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.