To install the extension

1. Download the extension script nbu_flexsnap_extension.tar.

   See Downloading the Snapshot Manager extension.

   Note:

   Do not create the authentication token yet, as it is valid only for 180 seconds.

2. If the host from which you want to install the extension is not the same host where your Snapshot Manager is installed, load the Snapshot Manager container images on the extension host (flexsnap-deploy, flexsnap-core, flexsnap-fluentd, flexsnap-datamover)

   The image names are in the following format:

   Example: veritas/flexsnap-deploy

3. Create image tags to map the source image with the target image, so that you can push the images to the Azure container registry. For more information, see Prerequisites to install the extension on a managed Kubernetes cluster in Azure.

   Gather the following parameters beforehand:

   Parameter	Description
   container_registry_path	To obtain the container registry path, go to your container registry in Azure and from the Overview pane, copy the 'Login server'. Example: mycontainer.azurecr.io
   tag	Snapshot Manager image version. Example: 10.1.x.xxxx

   • To tag the images, run the following command for each image, depending on the container platform running on your host:

     For Docker: # docker tag source_image:tag target_image:tag

     For Podman: # podman tag source_image:tag target_image:tag

     Where,

     • the source image tag is: veritas/flexsnap-deploy:tag>

     • the target image tag is: <container_registry_path>/<source_image_name>:<SnapshotManager_version_tag>

     Example:

     # docker tag veritas/flexsnap-deploy:10.1.x.xxxx 
     mycontainer.azurecr.io/veritas/flexsnap-deploy:10.1.x.xxxx
     # docker tag veritas/flexsnap-core:10.1.x.xxxx 
     mycontainer.azurecr.io/veritas/flexsnap-core:10.1.x.xxxx
     # docker tag veritas/flexsnap-fluentd:10.1.x.xxxx 
     mycontainer.azurecr.io/veritas/flexsnap-fluentd:10.1.x.xxxx
     # docker tag veritas/flexsnap-datamover:10.1.x.xxxx 
     mycontainer.azurecr.io/veritas/flexsnap-datamover:10.1.x.xxxx

4. Then to push the images to the container registry, run the following command for each image, depending on the container platform running on your host:

   For Docker: # docker push target_image:tag

   For Podman: # podman push target_image:tag

   Example:

   # docker push mycontainer.azurecr.io/veritas/
   flexsnap-deploy:10.1.x.xxxx
   # docker push mycontainer.azurecr.io/veritas/
   flexsnap-core:10.1.x.xxxx
   # docker push mycontainer.azurecr.io/veritas/
   flexsnap-fluentd:10.1.x.xxxx
   # docker push mycontainer.azurecr.io/veritas/
   flexsnap-datamover:10.1.x.xxxx
   

5. Once the images are pushed to the container registry, execute the extension script cp_extension.sh that was downloaded earlier, from the host where kubectl is installed. The script can be executed either by providing all the required input parameters in one command, or in an interactive way where you will be prompted for input.

   Gather the following parameters before running the script:

   Parameter	Description
   snapshotmanager_ip	Provide IP address or FQDN of the main Snapshot Manager host.
   target_image:tag	Target image tag created for the flexsnap-deploy image in step 3. Example: 'mycontainer.azurecr.io/veritas/flexsnap-deploy:10.0.1.0.10014'
   namespace	Snapshot Manager namespace that was created earlier in the preparation steps.
   tag_key=tag_val	tag_key and tag_val can be retrieved by using these commands: Get the name of the node: # kubectl get nodes | grep <node_name> Get the tag key=value label: # kubectl describe node <node_name> -n <namespace> | grep -i labels Output example: agentpool=cpuserpool
   storage_class	Kubernetes storage class that was created earlier in the preparation steps. Example: cloudpoint-sc
   Size in GB	Volume size to be provisioned as per your scaling requirements.
   workflow_token	Authentication token created from the NetBackup Web UI - Add extension dialog. See Downloading the Snapshot Manager extension.

   Note:

   While deploying Snapshot Manager Kubernetes extension, create a storage class and provide it as an input to the Snapshot Manager extension installation script. By default file properties are open, hence it is recommended to create storage class by providing custom attributes in order to maintain the file/folder permissions created on extension under /cloudpoint directory. For more information, see Create a storage class section of the Azure product documentation.

   Run the script as an executable file:

   • Permit the script to run as an executable:

     # chmod +x cp_extension.sh

   • Run the installation command with all the input parameters described in the above table:

     ./cp_extension.sh install -c <snapshotmanager_ip> -i <target_image:tag> -n <namespace> -p <tag_key=tag_val> -s <storage_class> -t <workflow_token> -k <Size (In GiB)>

     Example:

     ./cp_extension.sh install
     Snapshot Manager image repository path. Format=<Login-server/image:tag>:
      cpautomation.azurecr.io/veritas/flexsnap-deploy:10.1.x.xxxx
     Snapshot Manager extension namespace: snapshot-manager
     Snapshot Manager IP or fully-qualified domain name: 10.244.79.38
     Node group/pool label with format key=value: agentpool=extpool
     Storage class name: azurefile
     Size in GiB (minimum 30 GiB, Please refer NetBackup Snapshot Manager 
     Install and Upgrade Guide for PV size): 50
     Snapshot Manager extension token:
     This is a fresh NetBackup Snapshot Manager Extension Installation
     
     Starting Snapshot Manager service deployment
     customresourcedefinition.apiextensions.k8s.io/
     cloudpoint-servers.veritas.com unchanged
     serviceaccount/cloudpoint-acc created
     clusterrole.rbac.authorization.k8s.io/cloudpoint-cloudpoint-yj created
     clusterrolebinding.rbac.authorization.k8s.io/
     cloudpoint-rolebinding-cloudpoint-yj created
     deployment.apps/flexsnap-operator created
     Snapshot Manager service deployment ...done
     
     Generating Snapshot Manager Custom Resource Definition object
     Waiting for deployment "flexsnap-operator" rollout to finish: 
     0 of 1 updated replicas are available...
     deployment "flexsnap-operator" successfully rolled out
     cloudpointrule.veritas.com/cloudpoint-config-rule created
     Snapshot Manager extension installation ...
     Operator operations passed
     Waiting for all components to come up ...Done
     Waiting for all components to come up ...Done
     

   Run the script as an interactive file:

   • Run the following command:

     # ./cp_extension.sh install

   • When the script runs, provide the input parameters as described in the above table:

     ./cp_extension.sh install
     Snapshot Manager image repository path. Format=<Login-server/image:tag>: 
     cpautomation.azurecr.io/veritas/flexsnap-deploy:10.1.x.xxxx
     Snapshot Manager extension namespace: snapshot-manager
     Snapshot Manager IP or fully-qualified domain name: 10.244.79.38
     Node group/pool label with format key=value: agentpool=extpool
     Storage class name: azurefile
     Size in GiB (minimum 30 GiB, Please refer NetBackup Snapshot Manager 
     Install and Upgrade Guide for PV size): 50
     Snapshot Manager extension token:
     This is a fresh NetBackup Snapshot Manager Extension Installation
     
     Starting Snapshot Manager service deployment
     customresourcedefinition.apiextensions.k8s.io/
     cloudpoint-servers.veritas.com unchanged
     serviceaccount/cloudpoint-acc created
     clusterrole.rbac.authorization.k8s.io/
     cloudpoint-cloudpoint-yj created
     clusterrolebinding.rbac.authorization.k8s.io/
     cloudpoint-rolebinding-cloudpoint-yj created
     deployment.apps/flexsnap-operator created
     Snapshot Manager service deployment ...done
     
     Generating Snapshot Manager Custom Resource Definition object
     Waiting for deployment "flexsnap-operator" rollout to finish:
      0 of 1 updated replicas are available...
     deployment "flexsnap-operator" successfully rolled out
     cloudpointrule.veritas.com/cloudpoint-config-rule created
     Snapshot Manager extension installation ...
     Operator operations passed
     Waiting for all components to come up ...Done
     Waiting for all components to come up ...Done
     

   Note:

   The output examples have been formatted to fit the screen.