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
Deciding where to run Snapshot Manager
You can deploy Snapshot Manager in the following ways:
Deploy Snapshot Manager in a cloud and manage assets in that cloud.
Deploy Snapshot Manager in a cloud and manage assets in multiple clouds.
Veritas recommends that you deploy Snapshot Manager on cloud to protect your cloud assets. If you wish to protect assets in a cloud, deploy the Snapshot Manager host instance in the same cloud environment.
Similarly, if you wish to protect on-premise assets, deploy the Snapshot Manager host in the same on-premise environment. For detailed information about the on-premise content, refer to the NetBackup Snapshot Manager for Data Center Administrator's Guide.
You can deploy Snapshot Manager in a NetBackup media server, but not in a NetBackup primary server.
If you install Snapshot Manager on multiple hosts, we strongly recommend that each Snapshot Manager instance manage separate resources. For example, two Snapshot Manager instances should not manage the same AWS account or the same Azure subscription. The following scenario illustrates why having two Snapshot Manager instances manage the same resources creates problems:
Snapshot Manager instance A and Snapshot Manager instance B both manage the assets of the same AWS account.
On Snapshot Manager instance A, the administrator takes a snapshot of an AWS virtual machine. The database on Snapshot Manager instance A stores the virtual machine's metadata. This metadata includes the virtual machine's storage size and its disk configuration.
Later, on Snapshot Manager instance B, the administrator restores the virtual machine snapshot. Snapshot Manager instance B does not have access to the virtual machine's metadata. It restores the snapshot, but it does not know the virtual machine's specific configuration. Instead, it substitutes default values for the storage size configuration. The result is a restored virtual machine that does not match the original.
If you host the Snapshot Manager and media server in the same host, do the following for proper functioning of the backup from snapshot jobs:
Assign distinct IPs and NBU client names to the Snapshot Manager and the media server so that they can obtain different NetBackup Certificates. This is required so as have different NetBackup host ID certificates for communication. Use the following configuration:
Configure host with two network adapters
Edit the
/etc/hosts
file and make entry as mentioned in the example below:<IP Address MediaServer Host1> < MediaServer Host1> <IP Address Snapshot Manager Host2> <Snapshot Manager Host2>
Provide the MediaServer Host1 which is mentioned in the
/etc/hosts
file during the Media server installation for Media server name.Similarly select the Snapshot Manager Host 2 from the
/etc/hosts
file during the Snapshot Manager installation with non-default port other than 443.Start Snapshot Manager and Media services and register it with NetBackup primary server.
Once the Snapshot Manager is registered, ensure that it has a different HOST DB entry.
Before performing the backup from snapshot jobs, perform the following optimization: DISABLE SHM and NOSHM. See: https://www.veritas.com/support/en_US/article.100016170
This will ensure that NetBackup does not use shared memory for communicating between NetBackup data mover processes.