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
Prerequisites for configuring the AWS plug-in
If the Snapshot Manager instance is deployed in the AWS cloud, do the following before you configure the plug-in:
Create an AWS IAM role and assign permissions that are required by Snapshot Manager.
See Configuring AWS permissions for Snapshot Manager.
For more information on how to create an IAM role, see AWS Identity and Access Management Documentation.
Attach the IAM role to the Snapshot Manager instance.
For more information on how to attach an IAM role, see AWS Identity and Access Management Documentation.
Note:
If you have deployed Snapshot Manager using the CloudFormation Template (CFT), then the IAM role is automatically assigned to the instance when the Snapshot Manager stack is launched.
For cross account configuration, from the AWS IAM console (IAM Console > Roles), edit the IAM roles such that:
A new IAM role is created and assigned to the other AWS account (target account). Also, assign that role a policy that has the required permissions to access the assets in the target AWS account.
The IAM role of the other AWS account should trust the Source Account IAM role (Roles > Trust relationships tab).
The Source Account IAM role is assigned an inline policy (Roles > Permissions tab) that allows the source role to assume the role (
"sts:AssumeRole") of the other AWS account.The validity of the temporary security credentials that the Source Account IAM role gets when it assumes the Cross Account IAM role is set to 1 hour, at a minimum (Maximum CLI/API session duration field).
If the assets in the AWS cloud are encrypted using AWS KMS Customer Managed Keys (CMK), then you must ensure the following:
If using an IAM user for Snapshot Manager plug-in configuration, ensure that the IAM user is added as a key user of the CMK.
For source account configuration, ensure that the IAM role that is attached to the Snapshot Managert instance is added as a key user of the CMK.
For cross account configuration, ensure that the IAM role that is assigned to the other AWS account (cross account) is added as a key user of the CMK.
Adding these IAM roles and users as the CMK key users allows them to use the AWS KMS CMK key directly for cryptographic operations on the assets. For more details, refer to the AWS documentation.
If the Snapshot Manager instance has instance metadata service (IMDsv2) enabled, then ensure that the HttpPutResponseHopLimit parameter is set to 2 for the VM.
If the value of HttpPutResponseHopLimit parameter is not set to 2, then the AWS calls to fetch the metadata from the Snapshot Manager containers created on the machine fails.
For more information on the IMDsv2 service, refer to Use IMDSv2.