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
Removing NetBackup Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
During uninstallation, the installer performs the following tasks on the NetBackup Snapshot Manager extension host:
Stops all the NetBackup Snapshot Manager containers that are running
Removes the NetBackup Snapshot Manager containers
To uninstall a VM-based extension
- For Docker environment:
Run the following command:
# 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:<version> uninstall
Example:
# sudo docker run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:<10.2.x.x.xxx> uninstall
Note:
This is a single command without any line breaks.
For Podman environment:
Run the following command:
# 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:<version> uninstall
Example:
# podman run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<10.2.x.x.xxx> uninstall
Note:
This is a single command without any line breaks.
Replace the following parameters as per your environment:
Parameter
Description
<version>
Represents the NetBackup Snapshot Manager product version that is installed on the host.
<full_path_to_volume>
Represents the path to the NetBackup Snapshot Manager data volume, which typically is
/cloudpoint. - If desired, remove the NetBackup Snapshot Manager container images from the extension host.
Use the following docker command to view the docker images that are loaded on the host and remove the NetBackup Snapshot Manager images based on their IDs.
# sudo docker images -a
# sudo docker rmi <image ID>
This completes the NetBackup Snapshot Manager extension uninstallation on a VM host.
To uninstall a managed Kubernetes cluster-based extension
- Execute the extension script
cp_extension.shthat was downloaded at the time of extension installation, from the host where kubectl is installed.Run the following command:
bash cp_extension.sh uninstall
Once the uninstallation is triggered, provide the namespace as an input, from which the extension services need to be uninstalled.
After the uninstallation, the provisioned cloud resources associated with the uninstalled extension can be terminated or removed.