Review these guidelines and tips before running Hyper-V backups.
• | A separate backup is created for each VM you select. |
• | A VM may be included in only one schedule. If you attempt to add a VM to a second schedule, you cannot save that schedule. Remove the VM from the first schedule before adding it to another. If the schedule was created by an SLA policy, remove the VM from the policy instead of editing the schedule directly. |
• | A scheduled or on-demand job can contain one or more VMs that reside on a single host. You cannot run a job that contains VMs from multiple hosts. Create a separate job for each host instead. |
• | For VMs hosted on Windows Server versions later than 2008 R2, backups are executed concurrently. The number of jobs that run concurrently varies by the resource load of the system, and Monitor the resource utilization on the Hyper-V server to determine whether its backups should be staggered. |
The following apply to Hyper-V clusters only:
• | Non-clustered VMs hosted on a cluster node do not display when you select the cluster. To protect these VMs, you must select the host node. |
• | VMs that are hosted on a cluster node, but are not configured as highly available (i.e. not part of the cluster) cannot be included in the same job as the clustered VMs. Instead, you must create a separate job for the node that hosts these non-clustered VMs. |
• | If multiple virtual machines in a clustered environment are running on Windows Server 2008 R2, the system serializes the backups. Jobs are queued but run one at a time. This is a Windows limitation. |