Migration and updating 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:

Disable Snapshot Manager from NetBackup.
Stop services on the Snapshot Manager VM.
Create and attach a volume to the Snapshot Manager VM:
- Create a new volume from AWS cloud console in the same region where nodegroup of NetBackup is there.
  Note:
  Copy and save the volume ID which would be used later.
- Attach the volume to Snapshot Manager VM. Create a file system and mount the volume:.
  For example,
```
mkdir /mnt/test/

mkfs.ext4 /dev/xvdg

mount /dev/xvdg /mnt/test/

mount | grep xvdg
```
- To check the mount point, use the following command:
  df -h
- Copy the contents from /cloudpoint/mongodb to the new volume.
  For example, cp -r /cloudpoint/mongodb/* /mnt/test/
- Copy flexsnap.conf and bp.conf configuration files to the VM from where cluster is accessible.
- Unmount and detach the volume from VM as follows:
  - To unmount: umount /mnt/test/
  - To detach navigate to the console and detach.

From Cluster Access VM perform the following steps:

Create configuration maps using the following command:
kubectl create cm --from-file=<path to flexsnap.conf > -n <environment namespace>
kubectl create cm nbuconf --from-file=<path to bp.conf>  -n <environment namespace>
Create Snapshot Manager credential Secret using the following command:
kubectl create secret generic cp-creds --from-literal=username='<username>' --from-literal=password='<password>' -n <environment-namespace>
Create static PV and PVCs using the volume.

Create StorageClass volume for EBS:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: gp2-reclaim
parameters:
  fsType: ext4
  type: gp2
provisioner: kubernetes.io/aws-ebs
reclaimPolicy: Retain
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumer

Create StorageClass volume for EFS:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: efs-sc
provisioner: efs.csi.aws.com
parameters:
  provisioningMode: efs-ap
  fileSystemId: <EFS ID>
  directoryPerms: "700"
reclaimPolicy: Retain
volumeBindingMode: Immediate

Note:

It is recommended to use a separate EFS for Snapshot Manager deployment and primary server catalog.

Create mongodb Persistent Volume and Persistent Volume Claim as follows:

mongodb_pv.yaml: 
 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mongodb-pv  <pv name>
spec:
  capacity:
    storage: 30Gi
  accessModes:
    - ReadWriteOnce
  awsElasticBlockStore:
    volumeID: aws://us-east-2a/vol-00de395edff9fa8fb  <need to give in this format aws://region/volumeID >
    fsType: ext4
  persistentVolumeReclaimPolicy: Retain
  storageClassName: gp2-reclaim  <storageclass name>
  volumeMode: Filesystem
  claimRef:
    apiVersion: v1
    kind: PersistentVolumeClaim
    name: <PVC name>
    namespace: <netbackup-environment>  
 
mongodb-pvc.yaml: 
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: mongodb-pvc
  namespace: <netbackup-environment>
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: gp2-reclaim <Storage class name>
  resources:
    requests:
      storage: 30Gi
  volumeName: mongodb-pv <PV name>

For more information, refer to Leveraging AWS EBS for Kubernetes Persistent Volumes.

Create mongodb Persistent Volume and Persistent Volume Claim by applying the above yamls file as follows:

kubectl apply -f <path_to_mongodb_pv.yaml>

kubectl apply -f <path_to_mongodb_pvc.yaml> -n <environment-namespace>

Ensure that the newly created PVC is bound to the PV.
For example, kubectl get pvc -n <netbackup-environment> | grep mongodb

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

cpServer:
  - name: cp-cluster-deployment
    tag: <version>
    containerRegistry: <container registry
    credential:
      secretName: cp-creds
    networkLoadBalancer:
      annotations:
        ipAddr: <IP address>
        fqdn: <FQDN>
    storage:
      log:
        capacity: <log size>
        storageClassName: <EFS based storage class>
      data:
        capacity: <mongodb PV size>
        storageClassName: <mongodb PV storage class>
    nodeSelector:
      #controlPlane:
        #nodepool: <Control node pool>
        #labelKey: <Control node label key>
        #labelValue: <Control node label value>
      dataPlane:
        nodepool: <Data node pool>
        labelKey: <Data node label key>
        labelValue: <Data node label value>

Apply the environment.yaml file using the following command:
kubectl apply -f <path to environment.yaml> -n <environment-namespace>
Re-register the Snapshot Manger from WebUI using the edit option of existing Snapshot Manager entry and provide reissue token if the Snapshot Manager name (fqdn/ip) is same as VM deployment. For more information on reissuing the token, refer to the following section:
“Reissue token”
Note:
Automatic cloud provider additions would be skipped, if there was any AWS plugin addition present pre-migration. User can manually add the cloud with specific region if needed. Ensure that cluster region is configured with the plugin, as it is required to obtain the cluster details and correctly calculate the capability of Snapshot Manager.

After migration, duplicate plug-in entries might be displayed in the NetBackup Web UI. Manually delete these duplicated plugin information from the /usr/openv/var/global/CloudPoint_plugin.conf file.

Updating Snapshot Manager

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 data size field 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.

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

Parameters	Edit during update	Edit during upgrade
name	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
cpServer.NodeSelector.ControlPlane	No	Yes
cpServer.NodeSelector.DataPlane	No	Yes
proxySettings: vx_http_proxy	No	Yes
proxySettings: vx_https_proxy	No	Yes
proxySettings: vx_no_proxy	No	Yes

Migration and updating of Snapshot Manager

Feedback

Feedback