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
Snapshot Manager host sizing recommendations
The Snapshot Manager host configuration depends primarily on the number of workloads and also the type of workloads that you wish to protect. It is also dependent on the maximum number of simultaneous operations running on the Snapshot Manager at its peak performance capacity.
Another factor that affects performance is how you use Snapshot Manager for protecting your assets. If you use the Snapshot Manager agentless option to discover and protect your assets, then the performance will differ depending on the type of workload.
With agentless, Snapshot Manager transfers the plug-in data to the application host, performs the discovery and configuration tasks, and then removes the plug-in package from the application host.
Veritas recommends the following configurations for the Snapshot Manager host:
Table: Typical Snapshot Manager host configuration based on the number of concurrent tasks
Workload metric | Snapshot Manager host configuration |
|---|---|
Up to 16 concurrent operational tasks | CPU: 2 CPUs Memory: 16 GB For example, in the AWS cloud, the Snapshot Manager host specifications should be an equivalent of a t3.xlarge instance. |
Up to 32 concurrent operational tasks | CPU: 4 - 8 CPUs Memory: 32 GB or more For example, in the AWS cloud, the Snapshot Manager host specifications should be an equivalent of a t3.2xlarge or a higher type of instance. |
General considerations and guidelines:
Consider the following points while choosing a configuration for the Snapshot Manager host:
To achieve better performance in a high workload environment, Veritas recommends that you deploy the Snapshot Manager host in the same location as that of the application hosts.
If you are using the agentless option, Veritas recommends that you allocate enough space to the
/tmpdirectory on the application host. Snapshot Manager uses this directory for extracting the plug-in configuration files.Depending on the number of workloads, the amount of plug-in data that is transmitted from the Snapshot Manager host can get really large in size. The network latency also plays a key role in such a case. You might see a difference in the overall performance depending on these factors.
If you wish to configure multiple workloads using the agentless option, then the performance will be dependent on factors such as the network bandwidth and the location of the Snapshot Manager host with respect to the application workload instances. You can, if desired, bump up the Snapshot Manager host's CPU, memory, and network configuration to achieve a performance improvement in parallel configurations of agentless application hosts.
In cases where the number of concurrent operations is higher than what the Snapshot Manager host configuration capacity can handle, Snapshot Manager automatically puts the operations in a job queue. The queued jobs are picked up only after the running operations are completed.