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
AWS plug-in configuration notes
The Amazon Web Services (AWS) plug-in lets you create, restore, and delete snapshots of the following assets in an Amazon cloud:
Elastic Compute Cloud (EC2) instances
Elastic Block Store (EBS) volumes
Amazon Relational Database Service (RDS) instances
Aurora clusters
Note:
Before you configure the AWS plug-in, make sure that you have configured the proper permissions so Snapshot Manager can work with your AWS assets.
Snapshot Manager supports the following AWS regions:
Table: AWS regions supported by Snapshot Manager
AWS commercial regions | AWS GovCloud (US) regions |
|---|---|
|
|
The following information is required for configuring the Snapshot Manager plug-in for AWS:
If Snapshot Manager is deployed on a on-premise host or a virtual machine:
Table: AWS plug-in configuration parameters
Snapshot Manager configuration parameter | AWS equivalent term and description |
|---|---|
Access key | The access key ID, when specified with the secret access key, authorizes Snapshot Manager to interact with the AWS APIs. |
Secret key | The secret access key. |
Regions | One or more AWS regions in which to discover cloud assets. |
Note:
Snapshot Manager encrypts credentials using AES-256 encryption.
If Snapshot Manager is deployed in the AWS cloud:
Table: AWS plug-in configuration parameters: cloud deployment
Snapshot Manager configuration parameter | Description |
|---|---|
For Source Account configuration | |
Regions | One or more AWS regions associated with the AWS source account in which to discover cloud assets. Note: If you deploy Snapshot Manager using the CloudFormation template (CFT), then the source account is automatically configured as part of the template-based deployment workflow. |
For Cross Account configuration | |
Account ID | The account ID of the other AWS account (cross account) whose assets you wish to protect using the Snapshot Manager instance configured in the Source Account. |
Role Name | The IAM role that is attached to the other AWS account (cross account). |
Regions | One or more AWS regions associated with the AWS cross account in which to discover cloud assets. |
When Snapshot Manager connects to AWS, it uses the following endpoints. You can use this information to create a allowed list on your firewall.
ec2.*.amazonaws.com
sts.amazonaws.com
rds.*.amazonaws.com
kms. *.amazonaws.com
ebs.*.amazonaws.com
iam.amazonaws.com
eks.*.amazonaws.com
autoscaling.*.amazonaws.com
(For DBPaaS protection) dynamodb.*.amazonaws.com
In addition, you must specify the following resources and actions:
ec2.SecurityGroup.*
ec2.Subnet.*
ec2.Vpc.*
ec2.createInstance
ec2.runInstances
If you are creating multiple configurations for the same plug-in, ensure that they manage assets from different Regions. Two or more plug-in configurations should not manage the same set of cloud assets simultaneously.
When multiple accounts are all managed with a single Snapshot Manager, the number of assets being managed by a single Snapshot Manager instance might get too large and it would be better to space them out.
To achieve application consistent snapshots, we would require agent/agentless network connections between the remote VM instance and Snapshot Manager. This would require setting up cross account/subscription/project networking.
Before you configure the plug-in, consider the following:
Snapshot Manager does not support AWS Nitro-based instances that use EBS volumes that are exposed as non-volatile memory express (NVMe) devices.
To allow Snapshot Manager to discover and protect AWS Nitro-based Windows instances that use NVMe EBS volumes, ensure that the AWS NVMe tool executable file,
ebsnvme-id.exe, is present in any of the following locations on the AWS Windows instance:To allow Snapshot Manager to discover and protect Windows instances created from custom/community AMI.
AWS NVMe drivers must be installed on custom or community AMIs. See this link.
Install the
ebsnvme-id.exeeither in%PROGRAMDATA%\Amazon\Toolsor%PROGRAMFILES%\Veritas\CloudpointFriendly device name must contain the substring "NVMe", or update in Windows registry for all NVMe backed devices.
Registry path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_NVMe&Prod_Amazon_Elastic_B\Property Name: FriendlyName
Value: NVMe Amazon Elastic B SCSI Disk Drive
You cannot delete automated snapshots of RDS instances and Aurora clusters through Snapshot Manager.
The application consistency of AWS RDS applications depend on the behavior of AWS. (AWS suspends I/O while backing up the DB instance).
This is a limitation from AWS and is currently outside the scope of Snapshot Manager.
All automated snapshot names start with the pattern
rds:.If you are configuring the plug-in to discover and protect AWS Nitro-based Windows instances that use NVMe EBS volumes, you must ensure that the AWS NVMe tool executable file, ebsnvme-id.exe, is present in any of the following locations on the AWS instance:
%PROGRAMDATA%\Amazon\ToolsThis is the default location for most AWS instances.
%PROGRAMFILES%\Veritas\CloudpointManually download and copy the executable file to this location.
System PATH environment variable
Add or update the executable file path in the system's PATH environment variable.
If the NVMe tool is not present in one of the mentioned locations, Snapshot Manager may fail to discover the file systems on such instances. You may see the following error in the logs:
"ebsnvme-id.exe" not found in expected paths!"
This is required for AWS Nitro-based Windows instances only. Also, if the instance is launched using the community AMI or custom AMI, you might need to install the tool manually.
Snapshot Manager does not support cross-account replication for AWS RDS instances or clusters, if the snapshots are encrypted using the default RDS encryption key (aws/rds). You cannot share such encrypted snapshots between AWS accounts.
If you try to replicate such snapshots between AWS accounts, the operation fails with the following error:
Replication failed The source snapshot KMS key [<key>] does not exist, is not enabled or you do not have permissions to access it.
This is a limitation from AWS and is currently outside the scope of Snapshot Manager.
If a region is removed from the AWS plug-in configuration, then all the discovered assets from that region are also removed from the Snapshot Manager assets database. If there are any active snapshots that are associated with the assets that get removed, then you may not be able perform any operations on those snapshots.
Once you add that region back into the plug-in configuration, Snapshot Manager discovers all the assets again and you can resume operations on the associated snapshots. However, you cannot perform restore operations on the associated snapshots.
Snapshot Manager supports commercial as well as GovCloud (US) regions. During AWS plug-in configuration, even though you can select a combination of AWS commercial and GovCloud (US) regions, the configuration will eventually fail.
Snapshot Manager does not support IPv6 addresses for AWS RDS instances. This is a limitation of Amazon RDS itself and is not related to Snapshot Manager.
For more information, refer to the AWS documentation.
Snapshot Manager does not support application consistent snapshots and granular file restores for Windows systems with virtual disks or storage spaces that are created from a storage pool. If a Microsoft SQL server snapshot job uses disks from a storage pool, the job fails with an error. But if a snapshot job for virtual machine which is in a connected state is triggered, the job might be successful. In this case, the file system quiescing and indexing is skipped. The restore job for such an individual disk to original location also fails. In this condition, the host might move to an unrecoverable state and requires a manual recovery.