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
- NetBackup Snapshot Manager host sizing recommendations
- NetBackup Snapshot Manager extension sizing recommendations
- Creating an instance or preparing the host to install NetBackup Snapshot Manager
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store NetBackup Snapshot Manager data
- Verifying that specific ports are open on the instance or physical host
- Preparing NetBackup Snapshot Manager for backup from snapshot jobs
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Before you begin installing NetBackup Snapshot Manager extensions
- Downloading the NetBackup Snapshot Manager extension
- Installing the NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup 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 providers
- Configuration for protecting assets on cloud hosts/VM
- Deciding which feature (on-host agent or agentless) of NetBackup Snapshot Manager is to be used for protecting the assets
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Configuring an application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- NetBackup Snapshot Manager assets protection
- 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
- About NetBackup Snapshot Manager upgrades
- Supported upgrade path
- Upgrade scenarios
- Preparing to upgrade NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager using patch or hotfix
- Migrating and upgrading NetBackup Snapshot Manager
- GCP configuration for migration from zone to region
- Post-upgrade tasks
- Post-migration tasks
- Uninstalling NetBackup Snapshot Manager
- Preparing to uninstall NetBackup Snapshot Manager
- Backing up NetBackup Snapshot Manager
- Unconfiguring NetBackup Snapshot Manager plug-ins
- Unconfiguring NetBackup Snapshot Manager agents
- Removing the NetBackup Snapshot Manager agents
- Removing NetBackup Snapshot Manager from a standalone Docker host environment
- Removing NetBackup Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
- Restoring NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the NetBackup 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
- Acknowledgment not received for datamover
- Upgrade of extension on AWS (EKS) fails when upgrading through script
- Backup from snapshot job fails with timeout error
Installing the extension on Azure (AKS)
Before you install the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure:
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 - 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.iotag
NetBackup Snapshot Manager image version.
Example:
10.2.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.2.x.xxxx mycontainer.azurecr.io/veritas/flexsnap-deploy:10.2.x.xxxx # docker tag veritas/flexsnap-core:10.2.x.xxxx mycontainer.azurecr.io/veritas/flexsnap-core:10.2.x.xxxx # docker tag veritas/flexsnap-fluentd:10.2.x.xxxx mycontainer.azurecr.io/veritas/flexsnap-fluentd:10.2.x.xxxx # docker tag veritas/flexsnap-datamover:10.2.x.xxxx mycontainer.azurecr.io/veritas/flexsnap-datamover:10.2.x.xxxx
- 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.2.x.xxxx # docker push mycontainer.azurecr.io/veritas/ flexsnap-core:10.2.x.xxxx # docker push mycontainer.azurecr.io/veritas/ flexsnap-fluentd:10.2.x.xxxx # docker push mycontainer.azurecr.io/veritas/ flexsnap-datamover:10.2.x.xxxx
- Once the images are pushed to the container registry, execute the extension script
cp_extension.shthat 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 NetBackup 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
NetBackup Snapshot Manager namespace that was created earlier in the preparation steps.
tag_key=tag_val
tag_keyandtag_valcan 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=cpuserpoolstorage_class
Kubernetes storage class that was created earlier in the preparation steps.
Example:
cloudpoint-scSize 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.
Note:
While deploying NetBackup Snapshot Manager Kubernetes extension, create a storage class and provide it as an input to the NetBackup 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
/cloudpointdirectory. 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.2.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.2.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.
This concludes the NetBackup Snapshot Manager extension installation on a managed Kubernetes cluster (in Azure cloud).
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 five pods, namely,
flexsnap-deploy-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxx, flexsnap-fluentd-collector-xxxandflexsnap-datamover-xxxxare in Running state:# kubectl get pods -n <namespace>
Example: # kubectl get pods -n cloudpoint-system