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. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section III. Monitoring and Management
  4. Monitoring NetBackup
  5. Allocating static PV for Primary and Media pods
  6. Expanding log volumes for primary pods
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Expanding log volumes for primary pods

To optimize and reduce the log sizes of the PV's of the decoupled services, execute the following steps:

To reduce the log size of the PV

  1. Stop the primary pods:
    • Untar the .tar for the kubernetes package, and within the untar folder, navigate to scripts/.

    • Navigate to the scripts folder inside the build folder (For example: VRTSk8s-netbackup-<version>/scripts).

    • Run the script cloudscale_restart.sh, with stop (as the input for action) and the netbackup namespace (for namespace parameter).

      For example: ./cloudscale_restart.sh stop <namespace> This script will pause the primary server CR and stop all the decoupled services.

  2. Manually delete the statefulsets:
    • After all the pods are scaled down, get the required list of statefulsets using the command:

      kubectl get sts -n <netbackup_namespace> | grep -e "nbatd" -e "nbmqbroker" -e "nbwsapp" -e "bpdbm" -e "policyjob" -e "policyjobmgr" -e "primary"

    • Delete the statefulsets using the command:

      kubectl delete statefulset <statefulset_names_obtained_above> -n <netbackup_namespace>

  3. List the log PVCs for primary pods:
    • Execute the command:

      kubectl get pvc -n <netbackup_namespace> | grep log | grep -ve "catalog" -ve "uss" -ve "media"

      For example: kubectl get pvc -n netbackup | grep log | grep -ve "catalog" -ve "uss" -ve "media"

  4. Expand the log PVCs
    • Expand the capacities of the above obtained log PVCs using the command:

      kubectl patch pvc <pvc_names_obtained_above> -n <netbackup_namespace> -p '{"spec":{"resources":{"requests":{"storage":"<Expanded_capacity>Gi"}}}}'

      For example: kubectl patch pvc logs-nbu-primary-0 -n netbackup -p '{"spec":{"resources":{"requests":{"storage":"35Gi"}}}}'

  5. Expand log volume size in primary server CR
    • Execute the command: helm upgrade cloudscale cloudscale.tgz -n <namespace>--reuse-values --set environment.primary.storage.log.capacity=35Gi

  6. Start decoupled services using the cloudscale_restart.sh script:
    • Navigate to the scripts folder inside the build folder (For example: VRTSk8s-netbackup-<version>/scripts).

    • Run the script cloudscale_restart.sh with start (as the input for action) and the netbackup namespace (for namespace parameter).

      For example: ./cloudscale_restart.sh start <namespace>

Feedback

Was this page helpful?
Previous

Allocating static PV for Primary and Media pods

Next

Recommendation for media server volume expansion

Feedback

Was this page helpful?