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
- 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
- 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
Assets by workload type
This section describes the procedure for scanning VMware, Universal shares, Kubernetes and Cloud VM assets for malware.
Ensure that you meet the following prerequisites:
The backups were performed with a storage server at NetBackup 10.1 or later.
Backup images are stored on MSDP storage only with instant access capability, for the supported policy type only.
The last backup must be successful.
You must have an RBAC role with permissions to perform malware scans.
To scan the supported assets for malware, perform the following:
- On left, select the supported workload under Workloads.
- Select the resource which has backups completed (for example, VMware/Cloud VM, Universal shares, Kubernetes and so on).
- Select Actions > Scan for malware.
- On the Malware scan page, perform the following:
Select the date range for the scan by selecting Start date/time and End date/time.
Select Scanner host pool
From the Select current status of malware scan list select one of the following:
Not scanned
Not infected
Infected
All
- Click Scan for malware.
Note:
The malware scanner host can initiate a scan of three images at the same time.
- After the scan starts, you can see the Malware Scan Progress on Malware Detection, the following fields are visible:
Not scanned
Not infected
Infected
Failed
Note:
Any backup images that fail validation are ignored.
In progress
Pending