NetBackup™ Snapshot Manager Install and Upgrade Guide
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- 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
- NetBackup Snapshot Manager cloud plug-ins
- NetBackup Snapshot Manager application agents and plug-ins
- Installing and configuring Snapshot Manager agent
- Configuring the Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- NetBackup protection plan
- 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
- Troubleshooting NetBackup Snapshot Manager
Restoring Snapshot Manager
You can restore Snapshot Manager using any of the following methods:
Recover Snapshot Manager using a snapshot you have in the cloud
Recover Snapshot Manager using a backup located on-premises
(Only for GCP cloud provider) Recover Snapshot Manager using GCP cross-project restore
To recover Snapshot Manager using a snapshot you have in the cloud
- Using your cloud provider's dashboard or console, create a volume from the existing snapshot.
- Create a new virtual machine with specifics equal to or better than your previous Snapshot Manager server.
- Install Docker/Podman on the new server.
- Attach the newly-created volume to this Snapshot Manager server instance.
- Create the Snapshot Manager installation directory on this server.
Use the following command:
# mkdir /full_path_to_cloudpoint_installation_directory
For example:
# mkdir /cloudpoint
- Mount the attached volume to the installation directory you just created.
Use the following command:
# mount /dev/device-name /full_path_to_cloudpoint_installation_directory
For example:
# mount /dev/xvdb /cloudpoint
- Verify that all Snapshot Manager related configuration data and files are in the directory.
Enter the following command:
# ls -l /cloudpoint
- Download or copy the Snapshot Manager installer binary to the new server.
- Install Snapshot Manager.
Use the following command:
(For Docker)
# 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 install
(For Podman)
# sudo podman run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/podman.sock:/var/run/podman.sock veritas/flexsnap-deploy:10.1.0.0.1005 install
Here,
10.1.0.0.1005
represents the Snapshot Manager version. Replace it as per your currently installed product version.Note:
This is a single command. Ensure that you enter the command without any line breaks.
The installation program detects an existing version of Snapshot Manager and re-installs all Snapshot Manager services without overwriting existing content.
Messages similar to the following are displayed on the command prompt:
Configuration started at time Wed May 13 22:20:47 UTC 2020 This is a re-install. Checking if a 1.0 release container exists ...
Note the line that indicates that the operation is a re-install.
- When the installation completes, you can resume working with Snapshot Manager using your existing credentials.
To recover Snapshot Manager using a backup located on-premise
- Copy the existing Snapshot Manager backup to the new Snapshot Manager server and extract it to the Snapshot Manager installation directory.
In the following example, because
/cloudpoint
was backed up, the command creates a new/cloudpoint
directory.# tar -zxf cloudpoint_dr.tar.gz -C /cloudpoint/
- Download or copy the Snapshot Manager installer binary to the new server.
- Install Snapshot Manager.
Use the following command:
(For Docker)
# 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 install
(For Podman)
# sudo podman run -it --rm -u 0 -v /cloudpoint:/cloudpoint -v /var/run/podman.sock:/var/run/podman.sock veritas/flexsnap-deploy:10.1.0.0.1005 install
Here,
10.1.0.0.1005
represents the Snapshot Manager version. Replace it as per your currently installed product version.Note:
This is a single command. Ensure that you enter the command without any line breaks.
The installation program detects an existing version of Snapshot Manager and re-installs all Snapshot Manager services without overwriting existing content.
Messages similar to the following are displayed on the command prompt:
Configuration started at time Wed May 13 22:20:47 UTC 2020 This is a re-install. Checking if a 1.0 release container exists ...
Note the line that indicates that the operation is a re-install.
- When the installation completes, you can resume working with Snapshot Manager using your existing credentials.
Note:
The zone of Snapshot Manager and node-pools of the extension must be same.
In case of cross-project restore, a provider must be configured for the region in which Snapshot Manager is installed. If Snapshot Manager is installed in
zone then a provider for region must be configured.Let the details of the first project in which Snapshot Manager is installed be:
Service-account =
Project-name =
Let the details of the second project be:
Service-account =
Project-name =
To recover Snapshot Manager using GCP cross-project restore
- Create a cross project role in other-service-account with the following permissions:
compute.snapshots.useReadOnly
compute.disks.create
Cloud KMS CryptoKey Encrypter/Decrypter
- Assign the above role to cp-host-service-account under the other-project project.
More Information