NetBackup™ Web UI Kubernetes Administrator's Guide
- Introducing the NetBackup web user interface
- Monitoring NetBackup
- Overview of NetBackup for Kubernetes
- Deploying and configuring the NetBackup Kubernetes operator
- Configuring clusters for Kubernetes
- Prerequisites for deployment
- Deploying the NetBackup Kubernetes operator
- Upgrading the NetBackup Kubernetes operator deployment
- Deleting a NetBackup Kubernetes operator deployment
- Operator configuration on NetBackup side
- Operator configuration on Kubernetes side
- Getting token for adding clusters
- About expired images
- Managing Kubernetes assets
- Protecting Kubernetes assets
- Recovering Kubernetes assets
- Troubleshooting Kubernetes issues
Backup stuck in InProgress state
Scenario 1: Happens if a Velero pod running in a Kubernetes cluster, restarts when a backup job is running.
Recommended Action:
Follow these steps in Velero documentation, to identify if the job is stuck or running slowly. See Velero documentation. Delete the NetBackup backup ("backups.netbackup.veritas.com") CRD job and the Velero backup ("backups.velero.io") CRD job.
Scenario 2: Snapshots are in UploadFailed state or uploads fail, which may result in retry of the upload job.
Recommended Action:
Verify the reason for the issue by looking at the datamanager logs (on the processing node) and the backup driver logs to identify the root cause of the upload errors. To enable NetBackup jobs, delete the NetBackup backup CR ("backups.netbackup.veritas.com"), this marks the backup jobs as failed. Also clean the corresponding velero backup job ("backups.velero.io"), snapshot job ("snapshots.backupdriver.cnsdp.vmware.com") and upload jobs ("uploads.datamover.cnsdp.vmware.com").