Search <book_title>...

NetBackup™ Web UI Kubernetes Administrator's Guide

Last Published: 2022-03-28

Product(s): NetBackup (10.0)

Configure settings

The Kubernetes settings let you configure the various aspects of the Kubernetes deployment.

Setting the Kubernetes resource limit

With this setting you can control the number of backups that can be performed simultaneously on Kubernetes clusters. There are two different default values for running snapshot and back from snapshot jobs 1 and 4 respectively.

For an example to run a snapshot only backup job, if you protect 20 assets, and you have set the limit to 5, only five 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.

The default value for snapshot job example 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.

Configuring 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.
  By default, the resource limit is 1 for the Backup jobs per cluster.
- Click Edit, next to Backup from Snapshot Jobs per Kubernetes Cluster.
  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 must enter the cluster name manually and then enter a value for the limit. 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.

For more details, See Datamover pods exceed the Kubernetes resource limit .

Configuring autodiscovery frequency

Autodiscovery keeps a count of the NetBackup protected assets in your clusters. This setting lets you set the frequency by which NetBackup runs autodiscovery to locate new assets in your clusters and gather count of the assets that are removed or deleted from the clusters.

Possible values are between 5 minutes to one year. The default value is 30 minutes.

To set the autodiscovery frequency

On the left, click Workloads > Kubernetes.
On top-right, click Kubernetes settings > Autodiscovery.
Click Edit, near Frequency.
Enter the number of hours after which NetBackup runs autodiscovery. Click Save.

Running full and incremental discovery

Once the Kubernetes cluster is added, auto discovery cycle is triggered to discover all the assets available on the Kubernetes cluster. The first auto discovery of the day is a full discovery and subsequent auto discoveries are incremental.

To run a discovery

On the left, click Workloads > Kubernetes.
On the Kubernetes clusters list, click the Actions menu (Vertical ellipsis dots) in the row of the cluster and click Discovery now.

Here, incremental discovery fetches only those NetBackup assets which are changed in the cluster since last discovery run. Therefore, the first discovery is full and all subsequent ones will be incremental discovery.

Configuring permissions

Using manage permissions, you can assign different access privileges to the user roles. For more information see the Managing role-based access control chapter in the NetBackup Web UI Administrator's Guide.