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™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  5. Migration and upgrade of Snapshot Manager
  7. Migration and upgrade of Snapshot Manager
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Migration and upgrade of Snapshot Manager

Migrating Snapshot Manager

Users can manually migrate Snapshot Manager registered with NetBackup to Kubernetes Service cluster environment by performing the following steps:

  1. Disable Snapshot Manager from NetBackup.

  2. Stop services on the Snapshot Manager VM.

  3. Create and attach a disk to the VM which will be used as PV for mongoDB:

    Note:

    Ensure that the minimum size of the new attached disk must not be less than the size of /cloudpoint/mongodb folder. The disk must be in the same region as that of the Snapshot Manager VM. Disk should not be partitioned.

    • Copy contents from /cloudpoint/mongodb to the new disk.

      Note down the resource ID of this disk which can be obtained from portal/az CLI. Format of the resource ID:/subscriptions/<subscription id>/resourceGroups/<disk RG name>/providers/Microsoft.Compute/disks/<disk name>

    • Copy flexsnap.conf and bp.conf configuration files to the VM from where cluster is accessible.

    • Detach the disk from VM and move it to cluster resources group (RG): MC_<clusterRG>_<cluster name>_<cluster_region>

    • From VM perform the following steps:

      • Create configuration maps using the following command:

        kubectl create cm agentconf --from-file=<path to flexsnap.conf > -n <application namespace>

        kubectl create cm nbuconf --from-file=<path to bp.conf>  -n <application namespace>

      • Create Snapshot Manager Secrets using the following command:

        kubectl create secret generic cp-creds --from-literal=username='<username>' --from-literal=password='<password>'

      • Create mongodb Persistent Volume and Persistent Volume Claim as follows:

        mongodb pv: 
 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: <pv name>
spec:
  capacity:
    storage: <Size of the disk>
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  storageClassName: <Storage class name>
  claimRef:
    name: mongodb-pvc
    namespace: < environment namespace>
  csi:
    driver: disk.csi.azure.com
    readOnly: false
    volumeHandle: <Resource ID of the disk>
    volumeAttributes:
      fsType: <FS type>
 
mongodb-pvc: 
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mongodb-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: <Disk size>
  volumeName: <PV-name>
  storageClassName: <storage class name>

      Note:

      After applying the above yaml's, ensure that the newly created PVC is bound to PV: #kubectl get pvc -n <application-namespace> | grep mongodb

  4. Ensure that the flexsnap-operator is deployed and running before applying the Snapshot Manager section with environment.yaml file.

    Deploying the operators manually

  5. Edit the environment.yaml file to upgrade NetBackup (primary/media/MSDP) and add section for Snapshot Manager as follows: 

    cpServer: 
  - name: cp-cluster-deployment  
    containerRegistry: acr.azurecr.io
    credential: 
      secretName: cp-creds
    networkLoadBalancer: 
      annotations: 
        service.beta.kubernetes.io/azure-load-balancer-internal: "true" 
      ipAddr: 1.2.3.4
      fqdn: cpserver.example.com
  
    storage: 
      log: 
        capacity: 10Gi
        storageClassName: standard
      data: 
        capacity: <Disk size mentioned in mongodb pv> 
        storageClassName: <<Storage class name mentioned in mongodb pv> 
    nodeSelector: 
      controlPlane: 
        nodepool: cpcontrol1
        labelKey: cp-node-label
        labelValue: cpcontrol1
      dataPlane: 
        nodepool: cpdata1
        labelKey: cp-node-label
        labelValue: cpdata1

  6. Apply the environment.yaml file using the following command:

    kubectl apply -f <path to environment.yaml>

  7. Re-register the Snapshot Manger from WebUI if the Snapshot Manager name (fqdn/ip) is same as VM deployment.

Updating/Upgrading Snapshot Manager

  • Update:

    User can update few parameters on the existing deployed Snapshot Manager by making changes in the cpServer section of environment.yaml file and apply it.

    Only log size and data size fields can be changed in cpServer section of CR. For update operation to work, set the value of allowVolumeExpansion parameter to true in the storage classes used.

  • Upgrade:

    If there is a change in the cpServer tag, then it would be considered as a Snapshot Manager upgrade. For upgrade only few parameters related to Snapshot Manager can be modified.

The following table lists the parameters that can be modified during update/upgrade of Snapshot Manager:

Parameters

Edit during update

Edit during upgrade

resourceNamePrefix

No

No

tag

No

Yes

containerRegistry

No

Yes

credential: secretName

No

No

networkLoadBalancer: annotations

No

Yes

networkLoadBalancer: fqdn

No

No

networkLoadBalancer: ipAddr

No

Yes

data.capacity

Yes

Yes

data.storageClassName

No

No

log.capacity

Yes

Yes

log.storageClassName

No

No

cpServer.NodeSelector.ControlPlane

No

Yes

cpServer.NodeSelector.DataPlane

No

Yes

Feedback

Was this page helpful?
Previous

Migration and upgrade of Snapshot Manager

Next

Deploying MSDP Scaleout

Feedback

Was this page helpful?