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
Add a Kubernetes cluster
Before you add a Kubernetes cluster in NetBackup, you must install and configure the Kubernetes operator in the cluster. Or else the validation of the cluster fails which further leads to fail the add cluster operation.
After Kubernetes operator configuration, you can add Kubernetes clusters in NetBackup and discover all the assets inside the cluster automatically.
To add a cluster
- On the left click Kubernetes, under Workloads.
- Click the Kubernetes clusters tab, click Add.
- In the Add Kubernetes cluster page, enter the following:
Cluster name: Enter a name for the cluster. The name should be a DNS resolvable value or an IP address. Example: cluster.sample.domain.com.
Port: Enter the Kubernetes API server port number.
Controller namespace: Enter the namespace where the NetBackup Kubernetes operator is deployed in the Kubernetes cluster. Example: kops-ns.
- Click Next. In the Manage credentials page, you can add credentials to the cluster.
To use an existing credential, choose Select from an existing credential, and click Next. In the next page, select the required credentials, and click Next.
To create a new credential, click Add credential, and click Next. In the Manage credentials page, enter the following:
Credential name: Enter a name of the credential.
Tag: Enter a tag to associate with the credential.
Description: Enter a description of the credential.
To add Kubernetes clusters in NetBackup you need a Certification Authority (CA) certificate and a token. CA certificate and a token of the backup service account is required for authorization and authentication of Kubernetes cluster. To get a CA certificate and token, run the following command in the Kubernetes cluster: kubectl get secret <[namespace-name]-backup-server-secret> -n <namespace name> -o yaml..
Token: Enter the authentication token value in Base64 encoded form.
CA certificate: Enter the CA certificate file contents.
- Click Next.
The credentials are validated and on successful validation, the cluster is added. After the cluster is added, autodiscovery runs to discover available assets in the cluster.
Note:
In NetBackup Kubernetes version 10.1, edit cluster operation fails with an error message. The recommended action to resolve this issue is to first delete the cluster and add the cluster again.