It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda MSP Knowledge Base

Creating a Hyper-V Standard Backup Set

  • Last updated on

Hyper-V Standard backup sets offer a complete, image-style backup of Hyper-V virtual machines. Hyper-V Standard backup sets can be stored online and/or locally, giving you the ability to have duplicate copies for improved disaster-recovery protection. This guide will show you how to configure Hyper-V backup sets.  


The following prerequisites should be met in order to ensure Hyper-V backups run successfully.

  • The Backup Agent must be installed directly on the Hyper-V host which houses the virtual machines you want to back up.
  • The virtual machines you intend to back up must have Integration Services up-to-date.
  • The virtual machines you intend to back up must not have any dynamic volumes at the guest level. The virtual hard drive can be dynamic (host level) since this requirement only applies to how the volumes within a virtual machine are formatted.
  • (Optional But Recommended) Have the Backup Agent service run with local administrator rights.

Intronis cannot currently back up clustered Hyper-V hosts. If you plan on backing up Hyper-V virtual machines housed on clustered hosts, we recommend you install the backup software on each individual virtual machine and create an image backup set.

For Hyper-V 2016, Windows XP and Nano Server are backed up in a crash-consistent state instead of an application-consistent state.

Hyper-V Standard Backup Overview

Hyper-V backups can be stored locally and in the cloud. When Hyper-V backups are stored locally, they are stored in a proprietary format (encrypted and compressed) and require a restore to access backed-up data.

When the backup agent is installed on the Hyper-V host, it can back up any virtual machine on that host. You can select any number of virtual machines to be backed up. However, a VM can only be included in one backup set at a time.

If you are backing up to the cloud, then ensure that each VM you need to back up has the most recent version of Integration Services (IS) installed. The Hyper-V host’s Integration Services also must be updated (if the host’s IS is older, then the backup fails).

You can schedule a backup set to run on a recurring schedule. The default is running once per night.

You can add more than one VM to a backup set, but, by default, only one virtual disk is processed at a time when the backup runs. You can change this behavior by increasing the number of concurrent Hyper-V worker threads on the System Page. Increasing the number of worker threads allows multiple disks to be backed up concurrently but may use more resources on the host.

Hyper-V backups copy a full, initial backup of selected VMs. After this initial backup, incremental backups containing only the changed portions of each VM are performed until the next full backup is scheduled.


For Hyper-V 2016, Windows XP and Nano Server are backed up in a crash-consistent state instead of an application-consistent state.  

Creating Hyper-V Standard Backup Sets 

To create a Hyper-V Standard backup set, perform the following steps.

  1. Navigate to the Computer page.
    The Computer page is displayed.
  2. Click the Backup tab.
    The Backup Selections page is displayed.
  3. In the Backup Type pane, click Hyper-V Standard.
    The Select page is displayed.
  4. Click the Backup Name to provide a new name for your backup set or accept the default.
  5. At the Select Storage Location section, click one of the following radio button options.
    • Local Only (Local Vault must be enabled, and a local subscription is required. Data is not backed up to the cloud.)
    • Online Only (An enabled Local Vault disables this option.)
    • Online and Local (Local Vault must be enabled.)
      The radio button you select is highlighted as shown in the example below.
  6. In the Current Selection pane, select the available virtual machines you would like to back up.


    Any VMs that already are included in other backup sets are grayed out.

    A warning icon is displayed for VMs that have not been upgraded.

    Clicking the arrow image010.jpg at the right of the items displays more VMs.
    Your selections are displayed in the right pane. Click the remove icon image012.jpg to remove any selections or clear the VM check box.


  7. After making your selections, click Next.
    The Schedule page is displayed.

  8. Accept or edit the default schedule.

    • The default schedule is by the week on every day starting at 11 p.m.
    • Multiple daily/weekly schedules are permitted (if they do not overlap).
    • The Allow to Finish check box is always selected and grayed-out.
    • Your schedule is displayed in the Schedule column. Click the remove icon image018.jpg to delete the schedule.
  9. After setting the schedule, click Next.
    The Retention page is displayed.
  10. Select the number of versions you wish to retain, and for how long.

    The default is 4 recoverable versions of backups at the storage location that are retained for 28 days.

  11. Optionally, select the Enable Advanced Archiving check box.
    The Advanced Archiving fields are displayed.
  12. Make your selections, click Save Rule, and then click Next.
    The Advanced page is displayed.


    You must specify a temporary folder located on a disk with sufficient space. Temporary space of 1 GB is recommended for Hyper-V backups.

  13. In the Temporary Folder field, accept the default, type a new path, or click the Browse button to locate the temporary folder that is used during backing up.
  14. In the Force Full Backups section, use the arrows to specify how often full backups are performed after incremental backups.


    The default full backup is every 21 incremental backups.

    Taking a full VM backup periodically ensures the stability of the backup chain. Full backups take longer to run but result in shorter incremental chains and potentially shorter recovery times.

  15. Optionally, in the Backup Mode section, select the Allow Crash-Consistent Backups check box.

    Crash-consistent backups do not preserve the integrity of data for open files of transactional applications on the VM guest OS and may result in data loss.


    A crash-consistent backup captures all the virtual machine's data at the same time.

    An application-consistent backup captures all the data including the data in memory and all transactions in process.

    The software attempts to make an application-consistent backup. If unable, a crash-consistent backup is created.

    Pre-Windows Server 2016 versions display a different backup mode option as shown below.


    When enabled, the virtual machine may become unavailable during the snapshot process.

    The software attempts an online backup first. If unable, an offline backup is created. The virtual machine is paused and put into a saved state while the snapshot is taken, and then the virtual machine resumes operation. VMs in a saved or a paused state can be backed up. The imported recovery VMs are in a saved state in both cases.

    Tip: This mode is useful if an online backup cannot be taken. For instance, if the guest VM has dynamic disks, this mode allows guest VMs to be backed up in a non-quiesced, offline state.

  16. Click Next.
    The Summary page is displayed.
  17. After reviewing your selections, click the Create Backup Set button.

    If you did not change the default backup set name when creating a new backup set, the following confirmation pop-up is displayed after clicking the Create Backup button.


    This feature allows you to create a unique name for the backup set. If you already changed the default backup set name, the pop-up is not displayed.

    Optionally, change the backup set name, and click Confirm.

  18. Your scheduled backup is displayed on the Backup Selections page.