NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
- Introduction
 - Section I. NetBackup Snapshot Manager for Cloud installation and configuration
- Preparing for NetBackup Snapshot Manager for Cloud installation
- Meeting system requirements
 - NetBackup Snapshot Manager host sizing recommendations
 - NetBackup Snapshot Manager extension sizing recommendations
 - Creating an instance or preparing the host to install NetBackup Snapshot Manager
 - Installing container platform (Docker, Podman)
 - Creating and mounting a volume to store NetBackup Snapshot Manager data
 - Verifying that specific ports are open on the instance or physical host
 - Preparing NetBackup Snapshot Manager for backup from snapshot jobs
 - OCI - iptables rules for backup from snapshot jobs
 
 - Deploying NetBackup Snapshot Manager for Cloud using container images
- Before you begin installing NetBackup Snapshot Manager
 - Installing NetBackup Snapshot Manager in the Docker/Podman environment
 - Installing NetBackup Snapshot Manager on CIS Level 2 v2 configured host
 - Securing the connection to NetBackup Snapshot Manager
 - Verifying that NetBackup Snapshot Manager is installed successfully
 - Restarting NetBackup Snapshot Manager
 
 - Deploying NetBackup Snapshot Manager for Cloud extensions
- Before you begin installing NetBackup Snapshot Manager extensions
 - Downloading the NetBackup Snapshot Manager extension
 - 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
 - Install extension using the Kustomize and CR YAMLs
 - Managing the extensions
 
 - NetBackup Snapshot Manager for cloud providers
- Why to configure the NetBackup Snapshot Manager cloud providers?
 - AWS plug-in configuration notes
- Prerequisites for configuring the AWS plug-in
 - Before you create a cross account configuration
 - Prerequisites for application consistent snapshots using AWS Systems Service Manager
 - Prerequisites for configuring AWS plug-in using VPC endpoint
 - AWS permissions required by NetBackup Snapshot Manager
 - Configuring AWS permissions for NetBackup Snapshot Manager
 
 - Google Cloud Platform plug-in configuration notes
- Prerequisites for configuring the GCP plug-in using Credential and Service Account option
 - Google Cloud Platform permissions required by NetBackup Snapshot Manager
 - Preparing the GCP service account for plug-in configuration
 - Configuring a GCP service account for NetBackup Snapshot Manager
 - GCP cross-project configuration
 - GCP shared VPC configuration
 
 - Microsoft Azure plug-in configuration notes
 - Microsoft Azure Stack Hub plug-in configuration notes
 - OCI plug-in configuration notes
 - Cloud Service Provider endpoints for DBPaaS
 
 - Configuration for protecting assets on cloud hosts/VM
- Deciding which feature (on-host agent or agentless) of NetBackup Snapshot Manager is to be used for protecting the assets
 - 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
- Configuring an application plug-in
 - Microsoft SQL plug-in
 - Oracle plug-in
 
 
 - Protecting assets with NetBackup Snapshot Manager's agentless feature
 
 - Snapshot Manager for cloud catalog backup and recovery
 - NetBackup Snapshot Manager for cloud assets protection
 - Volume encryption in NetBackup Snapshot Manager for cloud
 - NetBackup Snapshot Manager for Cloud security
 
 - Preparing for NetBackup Snapshot Manager for Cloud installation
 - Section II. NetBackup Snapshot Manager for Cloud maintenance
- NetBackup Snapshot Manager for Cloud logging
 - Upgrading NetBackup Snapshot Manager for Cloud
- About NetBackup Snapshot Manager for Cloud upgrades
 - Supported upgrade path
 - Upgrade scenarios
 - Preparing to upgrade NetBackup Snapshot Manager
 - Upgrading NetBackup Snapshot Manager
 - Upgrading NetBackup Snapshot Manager using patch or hotfix
 - Applying operating system patches on NetBackup Snapshot Manager host
 - Migrating and upgrading NetBackup Snapshot Manager
 - GCP configuration for migration from zone to region
 - Post-upgrade tasks
 - Post-migration tasks
 
 - Uninstalling NetBackup Snapshot Manager for Cloud
- Preparing to uninstall NetBackup Snapshot Manager
 - Backing up NetBackup Snapshot Manager
 - Unconfiguring NetBackup Snapshot Manager plug-ins
 - Unconfiguring NetBackup Snapshot Manager agents
 - Removing the NetBackup Snapshot Manager agents
 - Removing NetBackup Snapshot Manager from a standalone Docker host environment
 - Removing NetBackup Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
 - Restoring NetBackup Snapshot Manager
 
 - Troubleshooting NetBackup Snapshot Manager for Cloud
- Troubleshooting NetBackup Snapshot Manager
 - SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the NetBackup 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
 - Acknowledgment not received for datamover
 - Google Cloud Platform does display the Snapshot ID of the disk
 - Application state of the connected/configured cloud VM(s) displays an error after upgrading to NetBackup Snapshot Manager version 11.x
 - Backup and restore jobs fail with timeout error
 - GCP restore with encryption key failed with an error message
 - Amazon Redshift clusters and databases not available after discovery
 - Shared VPC subnet not visible
 - Container manager may not spawn the ephemeral registration container timely
 - GCP restore from VM fails to obtain firewall rules
 - Parameterised VM restore fails to retrieve encryption keys
 - Restore from snapshot of a VM with security type Trusted Launch fails
 - Snapshot Manager failed to retrieve the specified cloud domain(s), against the specified plugin instance
 - Issues with SELinux configuration
 - Performance issues with OCI backup from snapshot and restore from backup copy
 - Connection to Amazon Linux 2023 or Alma Linux machines fail
 - Single file restore from snapshot copy fails with an error
 - MS SQL application backup, restore, or SFR job on Windows cloud VM fails with an error
 - Status 49 error appears
 - Restore from backup fails with an error
 - (For AWS) If the specified AMI is not subscribed in the given region an error message appears
 - Restore of Azure Disk Encrypted VM fails with an error
 
 
 
OCI permissions required by NetBackup Snapshot Manager
The table lists the required permissions.
Table:
Permissions  | Description  | 
|---|---|
BOOT_VOLUME_BACKUP_CREATE  | To take snapshots of the boot volume.  | 
BOOT_VOLUME_BACKUP_DELETE  | To delete the snapshot of the boot volume as per policy.  | 
BOOT_VOLUME_BACKUP_INSPECT  | To fetch the list of boot volume backup in the discovery.  | 
BOOT_VOLUME_BACKUP_READ  | To create boot volume from backup.  | 
COMPARTMENT_INSPECT  | To list availability domains, and to retrieve all the compartments in the tenancy.  | 
INSTANCE_ATTACH_VOLUME  | To attach the volume to the instance while restore.  | 
INSTANCE_CREATE  | To restore the instance.  | 
INSTANCE_DELETE  | To create and delete the instance that is created for boot volume restore from backup copy.  | 
INSTANCE_DETACH_VOLUME  | To detach volume after backup and restore operation.  | 
INSTANCE_IMAGE_INSPECT  | To fetch the OS details of the instance.  | 
INSTANCE_INSPECT  | To list various attachments like VNIC, volume, and so on.  | 
INSTANCE_POWER_ACTIONS  | To stop or start the instance during parameterized restore.  | 
INSTANCE_READ  | To list the instances in discovery and retrieve the details of the instance.  | 
INSTANCE_UPDATE  | Update the tags attached on the instance.  | 
KEY_ASSOCIATE  | To attach CMK in the parameterized restore.  | 
KEY_DISASSOCIATE  | To detach the CMK in the parameterized restore.  | 
KEY_INSPECT  | To list the keys in the vault.  | 
KEY_READ  | To get the key details.  | 
NETWORK_SECURITY_GROUP_READ  | List the network security group for parameterized restore.  | 
NETWORK_SECURITY_GROUP_UPDATE_MEMBERS  | To attach a network security group to an instance.  | 
SUBNET_ATTACH  | To launch the instance in a specific subnet.  | 
SUBNET_DETACH  | To terminate the instance in a specific subnet.  | 
SUBNET_READ  | To list subnets in parameterized restore.  | 
TAG_NAMESPACE_CREATE  | To create the tag namespace for NetBackup Snapshot Manager.  | 
TAG_NAMESPACE_INSPECT  | To check if the NetBackupSnapshot Manager tag namespace exists or not.  | 
TAG_NAMESPACE_USE  | To create the tag in the NetBackupSnapshot Manager tag namespace.  | 
TENANCY_INSPECT  | To get the details of the tenancy.  | 
VAULT_INSPECT  | To list the vaults and retrieve the keys.  | 
VCN_READ  | To get VCN details associated with the instance.  | 
VNIC_ASSOCIATE_NETWORK_SECURITY_GROUP  | To associate the network security group while launching the instance.  | 
VNIC_ATTACH  | To launch the instance.  | 
VNIC_ATTACHMENT_READ  | To list the VNIC attachment.  | 
VNIC_CREATE  | To associate VNIC to the instance while launching the instance.  | 
VNIC_DELETE  | To delete the associated VNIC to delete the instance.  | 
VNIC_READ  | To fetch the VNIC information associated with the instance.  | 
VOLUME_ATTACHMENT_CREATE  | To attach the volume after restore.  | 
VOLUME_ATTACHMENT_DELETE  | To attach the volume after restore.  | 
VOLUME_ATTACHMENT_INSPECT  | To detach the volume after backup and restore.  | 
VOLUME_BACKUP_CREATE  | To take snapshots of the volume.  | 
VOLUME_BACKUP_DELETE  | To delete the snapshot of the volume as per policy.  | 
VOLUME_BACKUP_INSPECT  | To retrieve the list of volume backups during discovery.  | 
VOLUME_BACKUP_READ  | List volume backups during the discovery.  | 
VOLUME_CREATE  | To create volumes during restore.  | 
VOLUME_DELETE  | To delete volumes during parameterized restore if the availability domain is changed.  | 
VOLUME_INSPECT  | To list volumes during discovery.  | 
VOLUME_UPDATE  | To update the tags and different attributes of the volume.  | 
VOLUME_WRITE  | Create volume from snapshot.  | 
Here is an example of assigning permissions to the policy that you create. Here, nbsm-iam-role is the name of dynamic group and NetBackup Snapshot Manager is a part of that dynamic group
Allow dynamic-group nbsm-iam-role to inspect compartments in tenancy
Allow dynamic-group nbsm-iam-role to inspect instance-images in tenancy
Allow dynamic-group nbsm-iam-role to inspect vnic-attachments in tenancy
Allow dynamic-group nbsm-iam-role to inspect vaults in tenancy
Allow dynamic-group nbsm-iam-role to read vcns in tenancy
Allow dynamic-group nbsm-iam-role to use keys in tenancy
Allow dynamic-group nbsm-iam-role to use subnets in tenancy where any { request.permission='SUBNET_DETACH', request.permission='SUBNET_ATTACH', request.permission='SUBNET_READ' }
Allow dynamic-group nbsm-iam-role to manage boot-volumes in tenancy where any { request.permission='BOOT_VOLUME_CREATE', request.permission='BOOT_VOLUME_DELETE', request.permission='BOOT_VOLUME_INSPECT', request.permission='BOOT_VOLUME_WRITE' }
Allow dynamic-group nbsm-iam-role to manage boot-volume-backups in tenancy where any { request.permission='BOOT_VOLUME_BACKUP_CREATE', request.permission='BOOT_VOLUME_BACKUP_DELETE', request.permission='BOOT_VOLUME_BACKUP_INSPECT', request.permission='BOOT_VOLUME_BACKUP_READ' , request.permission='BOOT_VOLUME_BACKUP_UPDATE' }
Allow dynamic-group nbsm-iam-role to manage instances in tenancy where any { request.permission='INSTANCE_ATTACH_VOLUME', request.permission='INSTANCE_CREATE', request.permission='INSTANCE_DELETE', request.permission='INSTANCE_DETACH_VOLUME', request.permission='INSTANCE_INSPECT', request.permission='INSTANCE_READ', request.permission='INSTANCE_POWER_ACTIONS', request.permission='INSTANCE_UPDATE' }
Allow dynamic-group nbsm-iam-role to manage network-security-groups in tenancy where any { request.permission='NETWORK_SECURITY_GROUP_READ', request.permission='NETWORK_SECURITY_GROUP_UPDATE_MEMBERS' }
Allow dynamic-group nbsm-iam-role to manage tag-namespaces in tenancy where any { request.permission='TAG_NAMESPACE_CREATE', request.permission='TAG_NAMESPACE_USE', request.permission='TAG_NAMESPACE_INSPECT' }
Allow dynamic-group nbsm-iam-role to manage volumes in tenancy where any { request.permission='VOLUME_CREATE', request.permission='VOLUME_DELETE', request.permission='VOLUME_INSPECT', request.permission='VOLUME_WRITE', request.permission='VOLUME_UPDATE' }
Allow dynamic-group nbsm-iam-role to manage volume-attachments in tenancy where any { request.permission='VOLUME_ATTACHMENT_CREATE', request.permission='VOLUME_ATTACHMENT_DELETE', request.permission='VOLUME_ATTACHMENT_INSPECT' }
Allow dynamic-group nbsm-iam-role to manage volume-backups in tenancy where any { request.permission='VOLUME_BACKUP_CREATE', request.permission='VOLUME_BACKUP_DELETE', request.permission='VOLUME_BACKUP_INSPECT'request.permission='VOLUME_BACKUP_READ', request.permission='VOLUME_BACKUP_UPDATE' }
Allow dynamic-group nbsm-iam-role to manage vnics in tenancy where any { request.permission='VNIC_ASSOCIATE_NETWORK_SECURITY_GROUP', request.permission='VNIC_ATTACH', request.permission='VNIC_CREATE', request.permission='VNIC_DELETE', request.permission='VNIC_READ' }
Allow dynamic-group nbsm-iam-role to use key-delegate in tenancy