Setting global limits on the use of Hyper-V resources
You can control the number of simultaneous backups that can be performed on a Hyper-V resource type in the Resource limits host property on the primary server. The settings apply to all NetBackup policies for the primary server.
For example, to avoid overloading the Hyper-V server, you can place a limit on the number of concurrent snapshots per server.
Note:
The resource limits only apply to policies that use automatic selection of virtual machines (Query Builder). If virtual machines are selected manually, the Resource limit settings have no effect.
Note:
To limit the number of simultaneous jobs per policy, use the setting on the policy Attributes tab. The effect of this option depends on how the policy selects virtual machines.
See Limit jobs per policy on the Attributes tab (for Hyper-V).
To set limits on the use of Hyper-V resources
- Open the NetBackup web UI.
- Click Hosts > Host properties. Select the primary server. If necessary click Connect. Then click Edit primary server.
- Expand Resource limits. Then click Hyper-V.
- Click in the Resource limit column to change the limit for a resource. The settings apply to all policies for the primary server.
For each resource type, the default is 0, No limit.
Table: Hyper-V resource types and limits describes the limits.
Table: Hyper-V resource types and limits
Resource type | Backup method | Resource limit |
|---|---|---|
Active Snapshots Per Server | VSS | Controls the maximum number of active backup jobs per Hyper-V server. Applies to a standalone Hyper-V server as well as to every Hyper-V server in a cluster. The typical setting for this resource type is 2. See the following examples. Example 1:
The NetBackup Activity Monitor shows 32 snapshot jobs. 12 snapshot jobs and their backup jobs are active. 20 snapshot jobs are queued. As active backup jobs are completed, queued snapshot jobs become active. Example 2:
The NetBackup Activity Monitor shows 64 snapshot jobs. 12 snapshot jobs for VMs on Node1 are active and another 12 snapshot jobs for VMs on Node2 are active. 40 snapshot jobs are queued. As active backup jobs are completed, queued snapshot jobs become active. |
Active Snapshots Per Cluster | VSS | Controls the maximum number of active backup jobs per Hyper-V cluster. The typical setting for this resource type is 4. Example 1:
The NetBackup Activity Monitor shows 60 snapshot jobs. For the VMs in the cluster, 20 snapshot jobs are active. 40 snapshot jobs are queued. As active backup jobs are completed, queued jobs become active. Example 2:
The NetBackup Activity Monitor shows 60 snapshot jobs. 10 snapshot jobs for the VMs in Node1 and Node2 are active. 50 snapshot jobs are queued. Even though the setting is higher, the setting controls the number of active jobs. |
Snapshot Operations Per Server | VSS | Controls the maximum number of simultaneous VSS operations such as create snapshot and delete snapshot on a Hyper-V server or a Hyper-V server in a cluster. Applies only during the snapshot creation and snapshot deletion phase of a backup. Does not control the number of simultaneous backup jobs. The typical setting for this resource type is 1. Each VM backup consists of a snapshot job and a subsequent backup job. Note: Snapshot Operations Per Server controls VSS snapshot creation and deletion, which are part of the snapshot job. When snapshot creation is completed, the backup job starts. When the backup job is active, the snapshot job is still shown as active even though the snapshot creation is completed. Therefore, this resource does not control the number of active backup jobs. See the following examples. Example 1:
The NetBackup Activity Monitor shows 32 snapshot jobs. 2 snapshot jobs are active and 30 snapshot jobs are queued. When the first snapshot job completes the snapshot creation, its backup job starts and the third snapshot job becomes active. When the second snapshot job completes snapshot creation, its backup job starts and the fourth snapshot job becomes active. When all the snapshots are created, there are 32 active backup jobs. Example 2:
The NetBackup Activity Monitor shows 32 snapshot jobs. 2 snapshot jobs are active and 30 snapshot jobs are queued. When the first snapshot job completes snapshot creation, its backup job starts and the third snapshot job becomes active. When the second snapshot job completes snapshot creation, its backup job starts and the fourth snapshot job becomes active. This process continues until there are 10 active snapshot jobs and their backup jobs. When the first backup job completes, the eleventh snapshot job becomes active, and so forth. |
Snapshot Operations Per Cluster | VSS | Controls the maximum number of simultaneous VSS operations such as create snapshot and delete snapshot within a cluster. Applies only during the snapshot creation and snapshot deletion phase of a backup. Does not control the number of simultaneous backup jobs. For example:
The NetBackup Activity Monitor shows 60 snapshot jobs. 5 snapshot jobs are active and 55 snapshot jobs are queued. When the first snapshot job completes snapshot creation, the corresponding backup job starts and the sixth snapshot job becomes active. When the second snapshot job completes snapshot creation, its backup job starts and the seventh snapshot job becomes active, and so forth. When 12 backup jobs are active, the thirteenth and following backup jobs are queued because is set to 12. |
Active Backups Per Hyper-V Server | WMI | Controls the maximum number of active backup jobs per Hyper-V server. Applies to a standalone Hyper-V server as well as to every Hyper-V server in a cluster. The typical setting for this resource type is 2. Example 1:
The NetBackup Activity Monitor shows 32 snapshot jobs. 12 snapshot jobs and their backup jobs are active. 20 snapshot jobs are queued. As active backup jobs are completed, queued snapshot jobs become active. Example 2:
The NetBackup Activity Monitor shows 40 snapshot jobs. 10 snapshot jobs for VMs on Node1 are active and 12 snapshot jobs for VMs on Node2 are active. 18 snapshot jobs are queued for the VMs on Node2. |
Active Backups Per Hyper-V Cluster | WMI | Controls the maximum number of active backup jobs per Hyper-V cluster. The typical setting for this resource type is 6. Example 1:
The NetBackup Activity Monitor shows 60 snapshot jobs. 20 snapshot jobs for VMs on the cluster are active. 40 snapshot jobs are queued. As active backup jobs are completed, queued snapshot jobs become active. Example 2:
The NetBackup Activity Monitor shows 60 snapshot jobs. 10 snapshot jobs for VMs on Node1 and Node2 are active. 50 snapshot jobs are queued. Even though the setting is higher, the setting controls the number of active jobs. |