Limiting concurrent CDP backup jobs
You can set a limit for the simultaneous CDP snapshot jobs that can run on the CDP gateway at a time. For example, if you protect 20 VMs and you set a limit of 5, then only 5 VMs can run simultaneous backups, and 15 VMs stay in queue. This setting is required for optimized use of your system and network resources. By default, the resource limit value is 0, representing no limit.
See Defining the CDP gateway . for information on how to do it on NetBackup version 10.0 onwards. For NetBackup 9.1 follow the procedure described below.
To set a resource limit, we have the following API:
POST /config/resource-limits
{
"data": [
{
"type": "resource-limits",
"id": "string",
"attributes": {
"resources": [
{
"resourceType": "string",
"resourceName": "string",
"resourceLimit": 0,
"additionalData": "string"
}
]
}
}
]
}
Here,
Idrepresents the workload, which isCdpresourceTypeshould beCdp-BackupresourceNamerepresents the CDP gateway host name. It should be the same as specified in the protection plan. If you keep an empty string forresourceName, theresourceLimitvalue is set as a global limit, which is applicable to all the configured CDP gateways.The
resourceLimitvalue sets the value of backup jobs for that gateway.
To retrieve the list of resource limits for a CDP workload type, use:
GET - /config/resource-limits/cdp
To update the value of resourceLimit for particular gateway, hit the POST API with the change in resourceLimit for the same record.
To delete the specified granular resource limits, use:
DELETE - /config/resource-limits
Only the resource limit set for a particular resource can be deleted. Provide both the resource type and the specific resource of that type.