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
 
 
Backing up Snapshot Manager
To back up Snapshot Manager when it is deployed in a cloud
- Stop Snapshot Manager services.Depending on the environment, use the following respective commands: (For Docker) # 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 stop (For Podman) # sudo podman run -it --rm -u 0 -v /full_path_to_volume_name:/full_path_to_volume_name -v /var/run/podman.sock:/var/run/podman.sock veritas/flexsnap-deploy:version stop Here, version represents the currently installed Snapshot Manager product version. You can retrieve the version using the following command: # cat /cloudpoint/version As an example following is the command for docker environment: # sudo docker run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:10.1.0.0.1005 stop Note: This is a single command. Ensure that you enter the command without any line breaks. 
- Ensure that all Snapshot Manager containers are stopped. This step is important because all activity and connections to and from Snapshot Manager must be stopped to get a consistent Snapshot Manager backup.Enter the following: (For Docker) # sudo docker ps | grep veritas (For Podman) # sudo podman ps | grep veritas This command should not return any actively running Snapshot Manager containers. 
- (Optional) If you still see any active containers, repeat step 2. If that does not work, run the following command on each active container:(For Docker) # sudo docker kill container_name (For Podman) # sudo podman kill container_name As an example following is the command for docker environment: # sudo docker kill flexsnap-api 
- After all the containers are stopped, take a snapshot of the volume on which you installed Snapshot Manager. Use the cloud provider's snapshot tools.
- After the snapshot completes, restart Snapshot Manager services.Use the following command: (For Docker) # 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 start (For Podman) # sudo podman run -it --rm -u 0 -v /full_path_to_volume_name:/full_path_to_volume_name-v /var/run/podman.sock:/var/run/podman.sock veritas/flexsnap-deploy:version start Here, version represents the currently installed Snapshot Manager product version. As an example following is the command for docker environment: # sudo docker run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:10.1.0.0.1005 start Note: This is a single command. Ensure that you enter the command without any line breaks. 
To backup Snapshot Manager when it is deployed on-premise
- Stop Snapshot Manager services.Use the following command: (For Docker) # 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 stop (For Podman) # sudo podman run -it --rm -u 0 -v /full_path_to_volume_name:/full_path_to_volume_name -v /var/run/podman.sock:/var/run/podman.sock veritas/flexsnap-deploy:version stop Here, version represents the currently installed Snapshot Manager product version. As an example following is the command for docker environment: # sudo docker run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:10.1.0.0.1005 stop Note: This is a single command. Ensure that you enter the command without any line breaks. 
- Ensure that all Snapshot Manager containers are stopped. This step is important because all activity and connections to and from Snapshot Manager must be stopped to get a consistent Snapshot Manager backup.Enter the following: (For Docker) # sudo docker ps | grep veritas (For Podman) # sudo podman ps | grep veritas This command should not return any actively running Snapshot Manager containers. 
- (Optional) If you still see any active containers, repeat step 2. If that does not work, run the following command on each active container:(For Docker) # sudo docker kill container_name (For Podman) # sudo podman kill container_name As an example following is the command for docker environment: # sudo docker kill flexsnap-api 
- Back up the folder /cloudpoint. Use any backup method you prefer.For example: # tar -czvf cloudpoint_dr.tar.gz /cloudpoint This command creates a compressed archive file named cloudpoint_dr.tar.gzthat contains the data in the/cloudpointdirectory.