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
Upgrading Snapshot Manager using patch or hotfix
You can also upgrade your current Snapshot Manager server using a patch or a hotfix. All the considerations and steps that apply for a normal upgrade, also apply to the upgrade being done using a patch or a hotfix, except that instead of downloading a new Snapshot Manager image, you download the patch/hotfix binaries.
Contact Veritas Technical Support at https://www.veritas.com/content/support/en_US/contact-us to obtain an Emergency Engineering Binary (EEB) for patch/hotfix.
Following are the brief steps explained with an example. For the detailed upgrade procedures
See Upgrading Snapshot Manager.
Consider that the currently installed version is Snapshot Manager 10.1.0.0 and you are upgrading to a Snapshot Manager patch version 10.1.0.0.1005 on a RHEL8.6 system in a Podman/Docker environment.
To upgrade Snapshot Manager using a patch or a hotfix
- Download the Snapshot Manager EEB obtained from Veritas Technical Support.
Example:
NetBackup_SnapshotManager_<version>.tar.gz - Un-tar the image file and list the contents:
# ls NetBackup_SnapshotManager_10.1.x.x.xxxx.tar.gz netbackup-flexsnap-10.1.x.x.xxxx.tar.gz flexsnap_preinstall.sh
- Run the following command to prepare the Snapshot Manager host for installation:
# sudo ./flexsnap_preinstall.sh
- Verify that there are no protection policy snapshots or other operations in progress and then stop 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 Snapshot Manager version.
- Depending on the environment, upgrade 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:<EEB_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:<EEB_version> install -yFor Docker
# 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> 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, EEB_version represents the Snapshot Manager patch/hotfix version you are upgrading to.
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.
- (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 Snapshot Manager version is installed successfully:
See Verifying that Snapshot Manager is installed successfully.
- This concludes the Snapshot Manager upgrade process using a patch or a hotfix . Verify that your Snapshot Manager configuration settings and data are preserved as is.