NetBackup™ Web UI 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
- Configure settings for NetBackup snapshot operation
- 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
- 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
- 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
- Restore from snapshot 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
Automated configuration of NetBackup protection for Kubernetes
Before configuring the NetBackup on the Kubernetes workload, you must run a NetBackup server with access to ports 443, 1556, and 13724.
NetBackup Kubernetes operator and data mover images must be uploaded to container registry accessible from the Kubernetes cluster.
You need to create a secret to be consumed for automated deployment.
To create a new API key, from NetBackup web UI.
- Go to Security > Access keys > Add. Enter the username and select the validity as one day to avoid misuse of API key.
- On the Kubernetes cluster, create a new secret, nb-config-deploy-secret.yaml, with the following content.
apiVersion: v1 kind: Secret metadata: name: <kops-namespace>-nb-config-deploy-secret namespace: <kops-namespace> type: Opaque stringData: apikey: <Enter the value of API key from the earlier step>
- Apply the secret. run the command kubectl apply -f nb-config-deploy-secret.yaml
Pre-installation
- Edit the following fields in
netbackupkops-helm-chart/values.yamlcontainers.manager.image: Container registry URL for pulling NetBackup Kubernetes controller image
imagePullSecrets: name: name of image pull secret if container registry requires authentication to pull images.
nbprimaryserver: Configured name of NetBackup primary server.
nbsha256fingerprint: Fetch sha256 fingerprint from the NetBackup web UI. Go to Security > Certificates > Certificate Authority
k8sCluster: FQDN for Kubernetes cluster API server.
k8sPort: Port on which the Kubernetes API server is listed.
The information is available on the UI console of Kubernetes cluster.
- If it is not present, run the following command to get Kubernetes cluster and Kubernetes port# kubectl cluster-infoKubernetes control plane runs at https://<Kubernetes FQDN>:6443
datamoverimage: Container registry URL to pull data mover image.
Storage parameters are required for snapshot and backup from snapshot operations. At least one of the Block or Filesystem storage parameters are mandatory.
- To get the storage classes, run the command # kubectl get storageclasses
storageclassblock: Storage class used for provisioning block volumes.
storageclassfilesystem: Storage class used for provisioning filesystem volumes.
- To get the volume snapshot class, run the command # kubectl get volumesnapshotclasses
volumesnapshotclassblock: Volume snapshot class for creating block volume snapshots.
volumesnapshotclassfilesystem: Volume snapshot class for creating filesystem volume snapshots.
waitTimeBeforeCleanupMinutes: Time in minutes to wait before configuration deployment is deleted in case of success. Max value can be set to 129600 (90 days). In case of failure, NetBackup resources of security token and credentials are deleted automatically but deployment runs to debug the failure.
To install helm, run the command# helm install veritas-netbackupkops <path to netbackupkops-helm-chart> -n <kops namespace>
To get the config-deploy pod from the Kubernetes operator namespace, run the command# kubectl get pod -n <kops namespace> | grep "config-deploy"
To check logs from the pod <namespace>-netbackup-config-deploy, run the command# kubectl logs <pod-name> -n <kops namespace>
It sets the log level of configuration pod. Values can be set to DEBUG, INFO or ERROR. Default value is set to INFO.
Note:
For more details, refer the Netbackup Kubernetes Quick Start Guide Release 10.3.