NetBackup™ Snapshot Manager Install and Upgrade Guide
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Meeting system requirements
- Snapshot Manager host sizing recommendations
- Snapshot Manager extension sizing recommendations
- Creating an instance or preparing the host to install Snapshot Manager
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store Snapshot Manager data
- Verifying that specific ports are open on the instance or physical host
- Preparing Snapshot Manager for backup from snapshot jobs
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Before you begin installing Snapshot Manager extensions
- Downloading the Snapshot Manager extension
- Installing the Snapshot Manager extension on a VM
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- Install extension using the Kustomize and CR YAMLs
- Managing the extensions
- NetBackup Snapshot Manager cloud plug-ins
- NetBackup Snapshot Manager application agents and plug-ins
- About the installation and configuration process
- Installing and configuring Snapshot Manager agent
- Configuring the Snapshot Manager application plug-in
- Configuring an application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- NetBackup protection plan
- Configuring VSS to store shadow copies on the originating drive
- Additional steps required after restoring an AWS RDS database instance
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Volume Encryption in NetBackup Snapshot Manager
- NetBackup Snapshot Manager security
- Preparing for NetBackup Snapshot Manager installation
- Section II. NetBackup Snapshot Manager maintenance
- NetBackup Snapshot Manager logging
- Upgrading NetBackup Snapshot Manager
- Uninstalling NetBackup Snapshot Manager
- Preparing to uninstall Snapshot Manager
- Backing up Snapshot Manager
- Unconfiguring Snapshot Manager plug-ins
- Unconfiguring Snapshot Manager agents
- Removing the Snapshot Manager agents
- Removing Snapshot Manager from a standalone Docker host environment
- Removing Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
- Restoring Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- Troubleshooting Snapshot Manager
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the Snapshot Manager host
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Discovery is not working even after assigning system managed identity to the control node pool
- Performance issue with GCP backup from snapshot
- Post migration on host agents fail with an error message
- File restore job fails with an error message
Installing the extension on GCP (GKE)
Before you install the 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 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 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 - 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
Snapshot Manager image version.
Example:
10.1.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.1.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-deploy:10.1.x.xxxx # docker tag veritas/flexsnap-core:10.1.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-listener:10.1.x.xxxx # docker tag veritas/flexsnap-fluentd:10.1.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-fluentd:10.1.x.xxxx # docker tag veritas/flexsnap-datamover:10.1.x.xxxx gcr.io/<project-name>/ veritas/flexsnap-datamover:10.1.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.1.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-core:10.1.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-fluentd:10.1.x.xxxx # docker push gcr.io/<project-name>/veritas/flexsnap-datamover:10.1.x.xxxx
- Finally, run the script
cp_extension.shthat was downloaded earlier.See Downloading the 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 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.1.x.xxxx
namespace
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 Snapshot Manager Kubernetes extension, create a persistent volume and provide it as an input to the 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 <cloudpoint-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>: cpautomation.gcr.io/ <project-name>/veritas/flexsnap-deploy:10.0.1.0.10012 Snapshot Manager extension namespace: <namespace-name> 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
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.1.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 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 > Snapshot Manager tab > click Advanced settings > go to Snapshot Manager extensions tab and verify.
Run the following command and verify that there are four pods, namely,
flexsnap-deploy-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.