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
Upgrading NetBackup Snapshot Manager extensions
When NetBackup Snapshot Manager is upgraded, all the extensions are automatically disabled. You must upgrade the extensions with the required NetBackup Snapshot Manager version and enable them manually from the NetBackup Web UI.
Upgrading NetBackup Snapshot Manager extensions on a managed Kubernetes cluster (AKS)
- Permit the script to run as an executable:
# chmod +x cp_extension_start.sh
- Run the command as follows:
# ./cp_extension.sh install
NetBackup Snapshot Manager image repository path. Format=<Login-server/image:tag>: bfsscale.azurecr.io/veritas/flexsnap-deploy:10.x.x.x.xxxx Snapshot Manager extension namespace: cloudpoint-system Snapshot Manager extension token: This is an upgrade of NetBackup Snapshot Manager Extension Starting Snapshot Manager service deployment customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com unchanged serviceaccount/cloudpoint-acc unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-cloudpoint-system unchanged clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-cloudpoint-system unchanged deployment.apps/flexsnap-deploy unchanged Snapshot Manager service deployment ...done customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met Generating Snapshot Manager Custom Resource Definition object deployment "flexsnap-deploy" successfully rolled out cloudpointrule.veritas.com/cloudpoint-config-rule configured Snapshot Manager extension installation ...done
Executable way
Permit the script to run as an executable:
# chmod +x cp_extension_start.sh
Run the installation command as follows:
# ./cp_extension_start.sh install -i <target_image:tag> -n <namespace> -t <workflow_token>
For example:
# ./cp_extension_start.sh install -i mycontainer.azurecr.io/veritas/flexsnap-deploy:10.2.x.x.xxxx -n cloudpoint-system -t workflow 3q3ou4jxiircp9tk0eer2g9jx7mwuypwz10k4i3sms2e7k4ee7-.....
Upgrade of NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
To improve the security in NetBackup 10.2, the processes in data mover container are configured to launch with service (non-root) user. If file share is created with the protocol then Backup from Snapshot, Index from Snapshot operations and so on would fail when data mover is launched for data movement operation. To resolve this issue, perform the following:
Take a backup of the logs from old file share or retain the old file share.
Uninstall the NetBackup Snapshot Manager extension. Delete , and from AKS extensions.
Install NetBackup Snapshot Manager extension. While defining consider using CSI provisioner for
Azure Fileswith NFS protocol.Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
Upgrade of NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
To improve the security in NetBackup 10.2, the processes in data mover container are configured to launch with service (non-root) user. If file share is created with the protocol then Backup from Snapshot, Index from Snapshot operations and so on would fail when data mover is launched for data movement operation. To resolve this issue, perform the following:
Take a backup of the logs from old file share or retain the old file share.
Uninstall the NetBackup Snapshot Manager extension. Delete , and from EKS extensions.
Install NetBackup Snapshot Manager extension. While defining consider to set
uid/gidto the root.Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
Upgrading NetBackup Snapshot Manager extensions on a VM
- Un-tar the image file and list the contents:
# ls NetBackup_SnapshotManager_10.2.x.x.xxxx.tar.gz netbackup-flexsnap-10.2.x.x.xxxx.tar.gz flexsnap_preinstall.sh
- Load required images:
For docker environments: # sudo docker load -i SnapshotManager_image_name
For podman environment, un-tar the image file:
# gunzip VRTSflexsnap-podman-10.x.x.x.x.tar.gz
- Run the following command to prepare the Snapshot Manager host for installation:
# ./flexsnap_preinstall.sh
- Run the following respective command to upgrade VM extension:
For docker environment:
# sudo docker run -it --rm -u 0 -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:<new_version> install_extension
For podman environment:
# sudo podman run -it --rm -u 0 -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<new_version> install_extension