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
Customization of datamover properties
You can customize datamover properties by passing key-value pairs in the backup server specific configmap.
Table: Datamover properties
Key Name | Possible Values |
|---|---|
VXMS_VERBOSE | Range:[0,99] |
VERBOSE | Range:[0,5] |
DTE_CLIENT_MODE |
|
USE_CTIME_FOR_INCREMENTALS | YES / NO |
USE_CTIME_FOR_DIRECTORY_INCRS | YES / NO |
DO_NOT_RESET_FILE_ACCESS_TIME | YES / NO |
Note:
Any other configuration setting that is supported by NetBackup client can be set for datamover by adding it under datamover.properties key in the datamover configmap. These configurations will be added in bp.conf file inside the datamover.
To update the configmap, add the key value pairs as follows:
apiVersion: v1
data:
datamover.properties: |
image=reg.domain.com/datamover/image:latest
VERBOSE=5
DTE_CLIENT_MODE=OFF
VXMS_VERBOSE=5
version: "1"
kind: ConfigMap
metadata:
name: backupserver.sample.domain.com
namespace: kops-nsStarting with NetBackup 10.5, TLS 1.3 protocol is supported. NetBackup 10.5 and later versions use TLS 1.3 protocol by default in secure communication workflows as follows:
secure proxy
data-in-transit encryption (DTE)
external KMS server
AD/LDAP server
MSDP
HTTPS communication using cURL
To configure TLS related properties, the required settings can be updated in this configmap. For more details about TLS settings refer the article.