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 NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager cloud providers
- Configuration for protecting assets on cloud hosts/VM
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- NetBackup Snapshot Manager assets protection
- 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
- Migrating and upgrading NetBackup Snapshot Manager
- Post-upgrade tasks
- Uninstalling NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
Prerequisites for configuring the AWS plug-in
If the NetBackup 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 NetBackup Snapshot Manager.
See Configuring AWS permissions for NetBackup 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 NetBackup 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 NetBackup Snapshot Manager using the CloudFormation Template (CFT), then the IAM role is automatically assigned to the instance when the NetBackup 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:
When selecting an IAM user to configure NetBackup 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 NetBackup Snapshot Manager 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 NetBackup 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 NetBackup Snapshot Manager containers created on the machine fails.
For more information on the IMDsv2 service, refer to Use IMDSv2.