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. Appendix B. MSDP Scaleout
  4. MSDP Scaleout maintenance
  5. Reinstalling MSDP Scaleout operator
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Reinstalling MSDP Scaleout operator

When you undeploy MSDP Scaleout operator, the MSDP Scaleout CRD is removed from the cluster. It also deletes all the existing MSDP Scaleout on the cluster. The PVC for the operator logs is also deleted. However, the MSDP Scaleout critical data and metadata is not deleted.

To reinstall MSDP Scaleout operator

  1. Navigate to cd $NB_DIR/bin directory.

    where NB_DIR is the directory where the tar file has been unzipped.

    Run the following command to delete the MSDP Scaleout operator:

    ./kubectl-msdp delete -n netbackup-operator-system

    -n: Namespace scope for this request.

  2. Run the following command to redeploy the operator.
    # helm upgrade --install operators operators-<version>.tgz \
          --create-namespace \
          --namespace netbackup-operator-system \
          --set global.platform=${platform} \
          --set global.operatorNamespace=netbackup-operator-system \
          --set global.containerRegistry="$REGISTRY" \
          --set global.storage.eks.fileSystemId=${EFS_ID} \
          --set msdp-operator.image.name="$MSDP_OPERATOR_IMAGE_NAME" \
          --set msdp-operator.image.tag="$MSDP_OPERATOR_IMAGE_TAG" \
          --set msdp-operator.storageClass.name=nb-disk-standardssd \
          --set msdp-operator.storageClass.size=5Gi \
          --set msdp-operator.logging.debug=false \
          --set msdp-operator.logging.age=28 \
          --set msdp-operator.logging.num=20 \
          --set msdp-operator.nodeSelector."${MSDP_NODE_SELECTOR_KEY//./\\.}"="${MSDP_NODE_SELECTOR_VALUE}" \
          --set nb-operator.image.name="$OPERATOR_IMAGE_NAME" \
          --set nb-operator.image.tag="$OPERATOR_IMAGE_TAG" \
          --set nb-operator.loglevel.value="0" \
          --set nb-operator.nodeSelector.node_selector_key="$MEDIA_NODE_SELECTOR_KEY" \
          --set nb-operator.nodeSelector.node_selector_value="$MEDIA_NODE_SELECTOR_VALUE" \
          --set flexsnap-operator.image.name="$FLEXSNAP_OPERATOR_IMAGE_NAME" \
          --set flexsnap-operator.image.tag="$FLEXSNAP_OPERATOR_IMAGE_TAG" \
          --set flexsnap-operator.nodeSelector.node_selector_key="$MEDIA_NODE_SELECTOR_KEY" \
          --set flexsnap-operator.nodeSelector.node_selector_value="$MEDIA_NODE_SELECTOR_VALUE"
  3. If the reclaim policy of the storage class is Retain, run the following command to restart the existing MSDP Scaleout. MSDP Scaleout starts with the existing data/metadata.

    kubectl apply -f <your-cr-yaml>

Feedback

Was this page helpful?
Previous

Logging in to the pods

Next

Migrating the MSDP Scaleout to another node pool

Feedback

Was this page helpful?