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
  3. NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
  5. Section II. NetBackup Snapshot Manager for Cloud maintenance
  7. Upgrading NetBackup Snapshot Manager for Cloud
  9. Post-upgrade tasks
  11. Upgrading NetBackup Snapshot Manager extensions
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

Upgrading NetBackup Snapshot Manager extensions

When NetBackup Snapshot Manager is upgraded, all the extensions are automatically disabled. You must upgrade the extensions with the required NetBackup Snapshot Manager version and enable them manually from the NetBackup Web UI.

Upgrading NetBackup Snapshot Manager extensions on a managed Kubernetes cluster (AKS)

  1. Permit the script to run as an executable:

    # chmod +x cp_extension_start.sh

  2. Run the command as follows:

    # ./cp_extension.sh install

    NetBackup Snapshot Manager image repository path. Format=<Login-server/image:tag>: bfsscale.azurecr.io/veritas/flexsnap-deploy:11.1.x.x.xxxx
Snapshot Manager extension namespace: cloudpoint-system
Snapshot Manager extension token:
This is an upgrade of NetBackup Snapshot Manager Extension

Starting Snapshot Manager service deployment customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com unchanged serviceaccount/cloudpoint-acc unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-cloudpoint-system unchanged clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-cloudpoint-system unchanged deployment.apps/flexsnap-deploy unchanged
Snapshot Manager service deployment ...done
  
customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met 
Generating Snapshot Manager Custom Resource Definition object deployment "flexsnap-deploy" successfully rolled out cloudpointrule.veritas.com/cloudpoint-config-rule configured
Snapshot Manager extension installation ...done

    Executable way

    • Permit the script to run as an executable:

      # chmod +x cp_extension_start.sh

    • Run the installation command as follows:

      # ./cp_extension_start.sh install -i <target_image:tag> -n <namespace> -t <workflow_token>

      For example:

      # ./cp_extension_start.sh install -i mycontainer.azurecr.io/veritas/flexsnap-deploy:11.1.x.x-xxxx -n cloudpoint-system -t workflow 3q3ou4jxiircp9tk0eer2g9jx7mwuypwz10k4i3sms2e7k4ee7-.....

Upgrade of NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure

To improve the security in NetBackup 10.4 or later, the processes in data mover container are configured to launch with service (non-root) user. If file share is created with the SMB protocol then Backup from Snapshot, Index from Snapshot operations and so on would fail when data mover is launched for data movement operation. To resolve this issue, perform the following:

  1. Take a backup of the logs from old file share or retain the old file share.

  2. Uninstall the NetBackup Snapshot Manager extension. Delete Persistent Volume, ConfigMap and Secrets from AKS extensions.

  3. Install NetBackup Snapshot Manager extension. While defining StorageClass consider using CSI provisioner for Azure Files with NFS protocol.

    Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure

Upgrade of NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS

To improve the security in NetBackup 10.4 or later, the processes in data mover container are configured to launch with service (non-root) user. If file share is created with the SMB protocol then Backup from Snapshot, Index from Snapshot operations and so on would fail when data mover is launched for data movement operation. To resolve this issue, perform the following:

  1. Take a backup of the logs from old file share or retain the old file share.

  2. Uninstall the NetBackup Snapshot Manager extension. Delete Persistent Volume, ConfigMap and Secrets from EKS extensions.

  3. Install NetBackup Snapshot Manager extension. While defining StorageClass consider to set uid/gid to the root.

    Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS

Upgrading NetBackup Snapshot Manager extensions on a VM

  1. Un-tar the image file and list the contents: 
    # ls
NetBackup_SnapshotManager_11.1.x.x-xxxx.tar.gz
netbackup-flexsnap-11.1.x.x-xxxx.tar.gz
flexsnap_preinstall.sh
  2. Run the following command to prepare the Snapshot Manager host for installation:

    # ./flexsnap_preinstall.sh

  3. Run the following respective command to upgrade VM extension:

    • Non interactive update of NetBackup Snapshot Manager extension::

      # flexsnap_configure install --extension

    • Interactive update of NetBackup Snapshot Manager extension:

      # flexsnap_configure install --extension -i

Feedback

Was this page helpful?
Previous

Post-upgrade tasks

Next

Post upgrade limitations

Feedback

Was this page helpful?