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
The following procedures describe how to upgrade your NetBackup Snapshot Manager deployment. During the upgrade, you replace the container that runs your current version of NetBackup Snapshot Manager with a newer container.
To upgrade NetBackup Snapshot Manager server in Podman/Docker environment
- Download the NetBackup Snapshot Manager upgrade installer.
On the NetBackup Snapshot Manager download page, click Download Now to download the NetBackup Snapshot Manager installer.
The NetBackup Snapshot Manager software components are available in a package form. The file name has the following format:
NetBackup_SnapshotManager_<version>.tar.gzNote:
The actual file name may vary depending on the release version.
- Copy the downloaded compressed image file to the computer on which you want to deploy NetBackup Snapshot Manager.
- 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
- Run the following command to prepare the NetBackup Snapshot Manager host for installation:
# sudo ./flexsnap_preinstall.sh
The output resembles the following:
Executing the following changes on this node to prepare the
NetBackup Snapshot Manager for installation: 1) Validate SELINUX 2) Loading Snapshot Manager service images. - Verify that there are no protection policy snapshots or other operations in progress and then stop NetBackup Snapshot Manager by running the following command:
For Podman
# podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<current_version> stopFor Docker
# docker run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/docker/docker.sock:/run/docker/docker.sock veritas/flexsnap-deploy:<current_version> stopHere, current_version represents the currently installed NetBackup Snapshot Manager version.
Note:
Ensure that you enter the command without any line breaks.
The NetBackup Snapshot Manager containers are stopped one by one. Messages similar to the following appear on the command line:
Stopping the services Stopping container: flexsnap-core-system-0-0 ...done Stopping container: flexsnap-core-indexing-0-0 ...done Stopping container: flexsnap-core-general-0-0 ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-nginx ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-scheduler ...done Stopping container: flexsnap-idm ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-core ...done Stopping container: flexsnap-api-gateway ...done Stopping container: flexsnap-certauth ...done Stopping container: flexsnap-rabbitmq ...done Stopping container: flexsnap-mongodb ...done Stopping container: flexsnap-fluentd ...done
Wait for all the NetBackup Snapshot Manager containers to be stopped and then proceed to the next step.
- Depending on the environment, upgrade NetBackup Snapshot Manager by running the following command:
For Podman
# podman run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<new_version> installFor an unattended installation, use the following command:
# podman run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<new_version> install -yFor Docker
# sudo docker run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:<new_version> installFor an unattended installation, use the following command:
# sudo docker run -it --rm --privileged -u 0 -v /cloudpoint:/cloudpoint -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:<new_version> install -y
Here, new_version represents the NetBackup Snapshot Manager version you are upgrading to, for example '10.2.x.x.xxxxx'
The -y option passes an approval for all the subsequent installation prompts and allows the installer to proceed in a non-interactive mode.
Note:
Ensure that you enter the command without any line breaks.
- The installer first loads the individual service images and then launches them in their respective containers.
The output resembles the following (Below is an example of the Podman environment output:
Installing the services Configuration started at time: Mon May 3 11:57:33 UTC 2021 podman server version: 2.0.5 Supported: true This is an upgrade to NetBackup Snapshot Manager 10.2.x.x.xxxxx Previous CloudPoint version: 10.2.x.x.xxxx Do you want to take a backup of the Snapshot Manager metadata prior to upgrade? (y/n): y Taking backup of Snapshot Manager metadata...done Backup completed successfully. Backup file located at /cloudpoint/backup/cloudpoint_10.2.x.x.xxxxx.tar.gz. [Storing /cloudpoint/keys/idm_store] [Storing /cloudpoint/keys/flexsnap-idm_store] Creating network: flexsnap-network ...done Starting container: flexsnap-fluentd ...done Starting container: flexsnap-mongodb ...done Starting container: flexsnap-rabbitmq ...done Starting container: flexsnap-certauth ...done Starting container: flexsnap-api-gateway ...done Starting container: flexsnap-core ...done Starting container: flexsnap-core ...done Starting container: flexsnap-core ...done Starting container: flexsnap-core ...done Starting container: flexsnap-scheduler ...done Starting container: flexsnap-core ...done Starting container: flexsnap-core ...done Starting container: flexsnap-idm ...done Starting container: flexsnap-deploy ...done Starting container: flexsnap-nginx ...done Upgrade finished at time: Mon May 3 11:58:51 UTC 2021 Before using backups from cloud snapshots, re-register Snapshot Manager with the NetBackup primary server
- (Optional) Run the following command to remove the previous version images.
(For Podman) # podman rmi -f <imagename>:<oldimage_tagid>
(For Docker) # docker rmi -f <imagename>:<oldimage_tagid>
- To verify that the new NetBackup Snapshot Manager version is installed successfully:
See Verifying that NetBackup Snapshot Manager is installed successfully.
- This concludes the upgrade process. Verify that your NetBackup Snapshot Manager configuration settings and data are preserved as is.