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 II. Deployment
  4. Deploying Cloud Scale
  5. Post Cloud Scale deployment tasks
  6. Restarting Cloud Scale Technology services
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Restarting Cloud Scale Technology services

Up to NetBackup versions 10.4 in the Cloud Scale Technology, the primary server deployment was performed in a monolithic way with all the services running in a single primary pod. Utilities like bp.kill_all and bp.start_all were used to start or stop the primary pod services.

NBPEM/NBJM and BPDBM NetBackup services are decoupled from the primary server. As there is no separate script to restart the decoupled primary services, perform the following steps:

To restart the Cloud Scale Technology services

  1. Navigate to the VRTSk8s-netbackup-<version>/scripts folder.
  2. Run the cloudscale_restart.sh script as follows:

    ./cloudscale_restart.sh <action> <namespace>

    Provide the namespace and the required action:

    • stop: Stops all the services under primary server (waits until all the services are stopped).

    • start: Starts all the services and waits until the services are up and running under primary server.

    • restart: Stops the services and waits until all the services are down. Then starts all the services and waits until the services are up and running.

    Note:

    Ignore if policy job pod does not come up in running state. Policy job pod would start once primary services start.

Feedback

Was this page helpful?
Previous

Post Cloud Scale deployment tasks

Next

Section III. Monitoring and Management

Feedback

Was this page helpful?