NetBackup™ for Kubernetes Administrator's Guide
- Overview of NetBackup for Kubernetes
- Deploying and configuring the NetBackup Kubernetes operator
- Prerequisites for NetBackup Kubernetes Operator deployment
- Deploy service package on NetBackup Kubernetes operator
- Port requirements for Kubernetes operator deployment
- Upgrade the NetBackup Kubernetes operator
- Delete the NetBackup Kubernetes operator
- Configure NetBackup Kubernetes data mover
- Automated configuration of NetBackup protection for Kubernetes
- Customize Kubernetes workload
- Troubleshooting NetBackup servers with short names
- Data mover pod schedule mechanism support
- Validating accelerator storage class
- Deploying certificates on NetBackup Kubernetes operator
- Managing Kubernetes assets
- Managing Kubernetes intelligent groups
- Managing Kubernetes policies
- Protecting Kubernetes assets
- Managing image groups
- Protecting Rancher managed clusters in NetBackup
- Recovering Kubernetes assets
- About incremental backup and restore
- Enabling accelerator based backup
- Enabling FIPS mode in Kubernetes
- About Openshift Virtualization support
- Troubleshooting Kubernetes issues
- Error during the primary server upgrade: NBCheck fails
- Error during an old image restore: Operation fails
- Error during persistent volume recovery API
- Error during restore: Final job status shows partial failure
- Error during restore on the same namespace
- Datamover pods exceed the Kubernetes resource limit
- Error during restore: Job fails on the highly loaded cluster
- Custom Kubernetes role created for specific clusters cannot view the jobs
- Openshift creates blank non-selected PVCs while restoring applications installed from OperatorHub
- NetBackup Kubernetes operator become unresponsive if PID limit exceeds on the Kubernetes node
- Failure during edit cluster in NetBackup Kubernetes 10.1
- Backup or restore fails for large sized PVC
- Restore of namespace file mode PVCs to different file system partially fails
- Restore from backup copy fails with image inconsistency error
- Connectivity checks between NetBackup primary, media, and Kubernetes servers.
- Error during accelerator backup when there is no space available for track log
- Error during accelerator backup due to track log PVC creation failure
- Error during accelerator backup due to invalid accelerator storage class
- Error occurred during track log pod start
- Failed to setup the data mover instance for track log PVC operation
- Error to read track log storage class from configmap
Create an intelligent group
Use the following procedure to create an intelligent group for Kubernetes workload in the NetBackup web UI.
Note:
With Virtualization support in Kubernetes, you can create intelligent groups with filtering the namespaces based on specific resource kinds. Virtual machines, Persistent volume, and Persistent volume claims are resource kinds available to filter.
To create an intelligent group
- On the left click Kubernetes, under Workloads.
- Click the Intelligent groups tab and then, click + Add.
- Enter a name and description for the group.
- Under Clusters section, click Add clusters
- In the Add clusters window, select one or multiple clusters from the list and click Select the selected clusters are added to the intelligent group.
Note:
Intelligent group can be created across multiple clusters. Ensure that you have the required permissions to add clusters in the group. To view and manage the group, the group administrator must have the view and manage permission for the selected clusters and groups.
- Under the Select assets section, do one of the following:
Select Include all assets.
This option uses a default query to select all assets for backup when the protection plan runs.
To select only the assets that meet specific conditions, create your own query: Click Add condition.
To add label conditions for the assets, click Add label condition to add
- To add a condition, use the drop-downs to select a keyword and operator and then enter a value.
To change the effect of the query, click + Condition and click AND or OR, then select the keyword, operator, and value for the condition.
Note:
To add label conditions, click Add label condition enter the label key and value.
Note:
You can choose to have only a label key in the condition without the label value. As value is optional parameter to add a label condition.
Note:
To add sub-query, click Add sub-query. You can add multiple level sub-queries.
- To test the query, click Preview.
The query-based selection process is dynamic. Changes in the Kubernetes cluster can affect which assets the query selects when the protection plan runs. As a result, the assets that the query selects later when the protection plan runs may not be identical to those currently listed in the preview.
Note:
When using queries in Intelligent groups, the NetBackup web UI might not display an accurate list of assets that match the query if the query condition has non-English characters.
Using the not equals filter condition on any attribute returns assets including those that have no value (null) present for the attribute.
Note:
When you click Preview or you save the group, the query options are treated as case-sensitive when the assets are selected for the group.
- To save the group without adding it to a protection plan, click Add.
- To save the group with adding it to a protection plan, click Add and protect.
- To subscribe the group to a protection plan, click Add protection.
Select the group and apply a protection plan to it, click Protect.
The selected asset group is successfully subscribed to the protection plan.
If you have a combination of conditions and labels, then you must first define a namespace condition and then a label condition.
Note:
For conditions, only a namespace value is allowed.