Please enter search query.
Search <book_title>...
NetBackup™ for Kubernetes Administrator's Guide
Last Published:
2025-04-14
Product(s):
NetBackup (11.0)
- 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
Configure storage units
You can configure all types of storage units for backup in a protection plan.
Note:
All storage types supported in Storage Lifecycle Policy (SLP) are supported for backup jobs.
To configure a storage unit for backup
- On the left, click Storage > Storage units.
- Click the Storage units tab and then click Add to add a storage unit configuration.
- Select the storage type from the list.
- Select a Category and then click Start.
- Enter the storage unit name in the Name field.
- In the Maximum concurrent jobs field, choose the maximum number for the backup jobs.
- In the Maximum fragment size field, choose the maximum number for the storage unit fragment size and then click Next.
- In Disk pool, select the disk pool you want to use in the storage unit and then click Next.
- The On demand only option specifies whether the storage unit is available exclusively on demand. A policy or schedule must be explicitly configured to use this storage unit.
- On the Media server tab, select the media servers that you want to use and then click Next. You can have NetBackup select your media server automatically or you can select your media servers manually using the radio buttons.
All media servers must of NetBackup version 10.0 or later
All media server managing the storage must have access to the selected Kubernetes clusters.
Media server must be able to connect with the API server. The port corresponding to the API server must be open for the outbound connection from the media server. The datamover pod must be able to connect to the media server.
- Review the setup of the storage unit and then click Save.
- To check details of a scheduled backup or backup now job, In the Activity monitor tab, click the Job ID, to view the backup job details. For file mode, you can see the total number of backed up files for every image in the Job Details section.