NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Configuring RBAC roles for VMware administrators
- Notes and prerequisites
- VMware vSphere privileges
- Managing VMware servers
- About VMware discovery
- Add VMware servers
- Change resource limits for VMware resource types
- Configuring backup policies for VMware
- Backup options on the VMware tab
- Exclude disks tab
- Configuring a VMware Intelligent Policy
- About the Reuse VM selection query results option
- Use Accelerator to back up virtual machines
- Configuring protection plans for VMware
- Malware scan
- Instant access
- Instant rollback
- Continuous data protection
- Backing up virtual machines
- VM recovery
- VMware agentless restore
- Restoring Individual files and folders from VMware backups
- Using NetBackup to back up Cloud Director environments
- Recover VMware Cloud Director virtual machines
- Restore virtual machines with Instant Recovery
- Protecting VMs using hardware snapshots and replication
- Best practices and more information
- Troubleshooting VMware operations
- NetBackup logging for VMware
- Snapshot error encountered (status code 156)
- Appendix A. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Appendix B. Backups of VMware raw devices (RDM)
Change resource limits for VMware resource types
VMware resource limits control the number of backups that can be performed simultaneously on a VMware resource type. The settings apply to all NetBackup policies for the primary server that you selected.
For example, to avoid overloading the ESX server, you can place a limit on the number of concurrent backup jobs per ESX server. To control I/O overhead on the datastore's array, you can limit the number of concurrent backups per datastore.
See Limitations on global limits for VMware resources.
To change the resource limits for VMware resource types
- Review the limitations for resource limits.
- On the left, click Workloads > VMware.
- On the top right, select VMware 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 resource type. This value is the global limit. The Override value indicates how many resources have any limits that are different from the global limit.
- Select the VMware resource type you want to change and then Edit.
See VMware resource types and limits.
Note: The Snapshot resource limit is different from the other resource types. It sets a limit for the number of simultaneous snapshot-only operations within a vCenter domain, such as create snapshot and delete snapshot. This limit applies only during the snapshot creation and snapshot deletion phases of a backup. It does not control the number of simultaneous backup jobs. This Snapshot limit can be useful for controlling the effect that multiple snapshot operations have on the vCenter server. Add a specific vCenter to override the global snapshot setting for that vCenter.
- Choose from the following options.
Set a global limit for a VMware resource type.
Locate the Global setting and select the Limits value that you want to apply.
This value limits the number of simultaneous backups that are performed for the resource type.
Set a limit for a specific VMware resource.
Click Add.
From the list, select the resource.
Select the Limits value that you want to apply.
This value limits the number of simultaneous backups that are performed for the selected resource.
At any point you can Click Reset default values to remove all the overrides and set all global VMware resource limits to their default values.
- Click Save.
- To enable resource limits for restores, select the Apply limits to restore jobs check box.
Note:
Restore resource limits are cumulative. The limit represents the number of combined backup and restores that can run simultaneously against a resource type. Restore resource limits only apply to vCenter, ESX server, and Datastore resource types.
Restores to ESXi clusters, datastore clusters, and storage policies do not count against resource limit settings. As VMware determines the placement of the VM once it is created.
The following limitations apply to setting global limits on the use of VMware 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.
The resource limits settings apply only to policies that use automatic selection of virtual machines (Query Builder). If virtual machines are selected manually on the Browse for Virtual Machines screen, the resource limit settings have no effect.
To limit the number of simultaneous jobs per policy, use the Attributes tab. The effect of this option depends on how the policy selects virtual machines.
setting on the policy