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™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
  3. Troubleshooting
  4. Resolving token issues
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Resolving token issues

Media server installation log displays the following error in /mnt/nblogs/setup-server.logs:

nbcertcmd: The -getCertificate operation
failed for server <primaryServerName>,
EXIT STATUS 5940: Reissue token is mandatory, 
please provide a reissue token

NetBackup media server and NetBackup primary server were in running state. Media server persistent volume claim or media server pod is deleted. In this case, reinstallation of respective media server can cause the issue.

To resolve token issues

  1. Open the NetBackup web UI using primary server hostname given in the primary server CR status.
  2. Navigate to Security > Host Mappings.
  3. Click Actions > Allow auto reissue certificate for the respective media server name.
  4. Delete data and logs PVC for respective media server only using the kubectl delete pvc <pvc-name> -n <namespace> command.

    The persisted data is deleted.

  5. Delete respective media server pod using kubectl delete <pod-name> -n <namespace> command.

    New media server pod and new PVCs for the same media server are created.

Feedback

Was this page helpful?
Previous

Resolving an issue of failed probes

Next

Resolving an issue related to insufficient storage

Feedback

Was this page helpful?