Change resource limits for Kuberentes resource types
With this setting you can control the number of backups that can be performed simultaneously on Kubernetes clusters. Kubernetes have two different default values to run the snapshot and backup from snapshot jobs 1 and 4 respectively.
Examples:
To run a snapshot only backup job, if you protect 20 assets, and you have set the limit to 5. Then only 5 assets can perform backup simultaneously, rest of the 15 assets stand in a queue. After one of the first 5 assets completes the backup, an asset from the queue takes its place.
To run a snapshot job, the default value for the resource limit is 1. Indicating that only one backup job per cluster can be in progress, while the rest of the assets are the queued state.
Configure this setting is recommended for optimized use of your system and network resources. The settings apply to all Kubernetes backups for the selected primary server.
To set the resource limit
- On the left, Workloads > Kubernetes.
- On top right, click Kubernetes settings > Resource limits.
- Do any of the following to set the resource limits:
Click Edit, next to Backup jobs per Kubernetes cluster. By default, the limit is 1.
This defines the amount of namespaces processed in parallel per cluster. Also, applies to the first operation to create a backup using snapshots for Backup from Snapshot jobs.
By default, the resource limit is 1 for the Backup jobs per cluster.
Click Edit, next to Backup from Snapshot Jobs per Kubernetes Cluster.
This defines the amount of namespaces backed up in parallel after snapshot creation per cluster. Each Backup from Snapshot will start a data mover pod in the NetBackup namespace on the cluster to process the data.
By default, the resource limit is 4 for the Backup from Snapshot jobs per cluster.
- In the Edit Kubernetes cluster dialog:
Enter a value in the Global field, to set a global limit for all the clusters. This limit denotes the number of Backup and Backup from Snapshot jobs that are performed simultaneously on a cluster.
You can add individual limits to the clusters that override the global limit for that cluster. To set individual limits to the clusters, click Add.
You can select the cluster available from the list and then enter a limit value for the selected cluster. You can add limits to each available cluster in your deployment.
Click Save to save the changes.
Note:
In the NetBackup 10.0 release, the data mover pods exceed the Kubernetes resource limit settings.