Change resource limits for KVM resource types
KVM resource limits control the number of backups that can be performed simultaneously on a KVM host. The settings apply to all NetBackup policies for the primary server that you selected.
For example, to avoid overloading the KVM host, you can place a limit on the number of concurrent backup jobs per KVM host with the setting .
To change the resource limits for KVM resource types
- Review the limitations for resource limits.
- On the left, select Workloads > KVM.
- On the top right, select KVM settings > Resource limits.
For each resource, the default value is 0 (No limit).
Limits indicates the number of simultaneous backups that can be performed for the KVM hosts or host. This value is the global limit. The Override value indicates how many KVM hosts have any limits that are different from the global limit.
- To change the limit for the resource Backup Jobs per KVM Host, select Edit.
- Choose from the following options.
Set a global limit for all KVM hosts.
Locate the Global setting and select the Limits value that you want to apply.
This value limits the number of simultaneous backups for all KVM hosts.
Set a limit for a specific KVM host.
Select Add.
From the list, enter the name of the KVM host.
Select the Limits value that you want to apply.
This value limits the number of simultaneous backups that are performed for the KVM host.
- Select Save.
At any point you can select Reset default values to remove all the overrides and set all global KVM resource limits to their default values.
The following example illustrates how these limits control simultaneous backups. The settings must be done according to KVM configuration in your environment. Consider a case where a KVM host hosts 20 VMs. When the job runs there are 20 concurrent jobs that start if no resource limit is set, which is default behavior. When the is set to 10, this limit is enforced and 10 backup jobs run concurrently.
The following limitations apply to setting global limits on the use of KVM resources:
New and changed resource limits may not take effect immediately. It can take a couple of jobs before the resource limit updates are in effect.
To limit the number of simultaneous jobs per policy, use the setting on the policy Attributes tab.