Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Kubernetes Administrator's Guide
  3. Troubleshooting Kubernetes issues
NetBackup™ for Kubernetes Administrator's Guide

Troubleshooting Kubernetes issues

This section includes the following topics:
  • 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

  • Restore operation fails when restoring single VM to a different cluster

  • Auto-deployment of the Kubernetes workload fails during backupservercert creation

  • Auto-deployment of the Kubernetes workload fails with time-out error

  • Fail Fast restore strategy fails with error 2890 K8s restore data operation failed.

Feedback

Was this page helpful?
Previous

Troubleshooting for virtualization

Next

Error during the primary server upgrade: NBCheck fails

Feedback

Was this page helpful?