Installing the extension on GCP (GKE)
Before you install the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP:
To install the extension
- Download the extension script
nbu_flexsnap_extension.tar.See Downloading the NetBackup Snapshot Manager extension.
Note:
Do not create the authentication token yet, as it is valid only for 180 seconds.
- If the host from which you want to install the extension is not the same host where your NetBackup Snapshot Manager is installed, load the NetBackup 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 - Tag the images to map the source image with the target image, so that you can push the images to the GCP container registry.
Gather the following parameters beforehand:
Parameter
Description
container_registry_path
To obtain the container registry path, go to your container registry in GCP and from the Overview pane, copy the 'Login server'.
Example:
gcr.io/<project-name>/<dir>tag
NetBackup Snapshot Manager image version.
Example:
10.3.x.xxxxTo 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.3.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-deploy:10.3.x.xxxx # docker tag veritas/flexsnap-core:10.3.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-listener:10.3.x.xxxx # docker tag veritas/flexsnap-fluentd:10.3.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-fluentd:10.3.x.xxxx # docker tag veritas/flexsnap-datamover:10.3.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-datamover:10.3.x.xxxx
- 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 gcr.io/<project-name>/veritas/flexsnap-deploy:10.3.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-core:10.3.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-fluentd:10.3.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-datamover:10.3.x.xxxx
- Finally, run the script
cp_extension.shthat was downloaded earlier.See Downloading the NetBackup Snapshot Manager extension.
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
cloudpoint_ip
Provide IP address or FQDN of the main NetBackup Snapshot Manager host.
target_image:tag
Target image tag created for the flexsnap-deploy image in step 3.
Example: gcr.io/<project-name>/veritas/flexsnap-deploy:10.3.x.xxxx
namespace
NetBackup Snapshot Manager namespace that was created earlier in the preparation steps.
tag_key=tag_val
tag_keyandtag_valcan be retrieved by using the following command:# gcloud container node-pools list --cluster=<cluster-name> --zone=<zone-name>
persistent_volume
Kubernetes persistent volume that was created earlier in the preparation steps.
Size in GiB
Volume size to be provisioned as per your scaling requirements.
workflow_token
Authentication token created from the NetBackup Web UI - Add extension dialog.
Note:
While deploying NetBackup Snapshot Manager Kubernetes extension, create a persistent volume and provide it as an input to the NetBackup Snapshot Manager extension installation script.
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 cloud.google.com/gke-nodepool=<nodepool-name> -v <persistent-volume-name> -k <size-in-GiB> -t <token>
Example:
# ./cp_extension.sh install Snapshot Manager image repository path. Format=<Login-server/image:tag>: gcr.io/cloudpoint-development/test/veritas/flexsnap-deploy:10.3.x.x.xxxxx Snapshot Manager extension namespace: test-ns Snapshot Manager IP or fully-qualified domain name: 10.347.30.142 Node group/pool label with format key=value: cloud.google.com/gke-nodepool= test-pool-dnd Persistent volume name: test-fileserver-pv Size in GiB (minimum 30 GiB, Please refer NetBackup Snapshot Manager Install and Upgrade Guide for PV size): 30 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 unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-shashwat-ns configured clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-shashwat-ns unchanged deployment.apps/flexsnap-operator created Snapshot Manager service deployment ...done customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met 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 [root@xxxx]# kubectl get pods NAME READY STATUS RESTARTS AGE flexsnap-fluentd-collector-79f4dd8447-5lgrf 1/1 Running 0 34s flexsnap-fluentd-xl7px 1/1 Running 0 33s flexsnap-listener-598f48d59b-crfjq 1/1 Running 0 33s flexsnap-operator-574dccc58f-fnkdf 1/1 Running 0 104s
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.gcr.io/ <project-name>/veritas/flexsnap-deploy:10.3.x.xxxx Snapshot Manager extension namespace: snapshot-manager Snapshot Manager IP or fully-qualified domain name: xx.xxx.xx.xx Node group/pool label with format key=value: agentpool=extpool Persistent volume name: 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.
This concludes the NetBackup Snapshot Manager extension installation on a managed Kubernetes cluster (in GCP).
To verify that the extension is installed successfully:
Verify that the success message is displayed at the command prompt.
Verify that the extension is listed on the NetBackup Web UI.
Go to Cloud > NetBackup Snapshot Manager tab > click Advanced settings > go to NetBackup Snapshot Manager extensions tab and verify.
Run the following command and verify that there are four pods, namely,
flexsnap-operator-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxxandflexsnap-fluentd-collector-xxxare in Running state:# kubectl get pods -n <namespace>
Example: # kubectl get pods -n cloudpoint-system
The
flexsnap-datamover-xxxxpod will not run by-default after deployment, it will get created only if backup operation is triggered.