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
 - Iptable rules for backup from snapshot jobs in OCI
 
 - 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 option
 - Prerequisites for configuring the GCP plug-in using 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
 
 - 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
 - Upgrade of extension on AWS (EKS) fails when upgrading through script
 - Backup and restore jobs fail with timeout error
 - GCP restore with encryption key failed with an error message
 - Amazon Redshift 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 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
 
 
 
Prerequisites for the agentless configuration
Have the following information with you:
Host username
Host password or SSH key
NetBackup Snapshot Manager requires these details to gain access to the host and perform requested operations.
On hosts where you want to configure this feature, grant password-less sudo access to the host user account that you provide to NetBackup Snapshot Manager.
NetBackup Snapshot Manager requires a host user account to connect and perform operations on the host. You must grant password-less sudo access to the user account that you provide to NetBackup Snapshot Manager. This is required for all the hosts where you want to configure the agentless feature.
Note:
The following steps are provided as a general guideline. Refer to the operating system or the distribution-specific documentation for detailed instructions on how to grant password-less sudo access to a user account.
Perform the following steps on the host where you want to configure the agentless feature.
Verify that the host username that you provide to NetBackup Snapshot Manager is part of the
wheelgroup.Log on as a root user and run the following command:
# usermod -aG wheel hostuserID
Here, hostuserID is the host username that you provide to NetBackup Snapshot Manager.
Log out and log on again for the changes to take effect.
Edit the
/etc/sudoersfile using the visudo command:# sudo visudo
Add the following entry to the
/etc/sudoersfile:hostuserID ALL=(ALL) NOPASSWD: ALLIn the
/etc/sudoersfile, edit the entries for thewheelgroup as follows:Comment out (add a # character at the start of the line) the following line entry:
# %wheel ALL=(ALL) ALL
Uncomment (remove the # character at the start of the line) the following line entry:
%wheel ALL=(ALL) NOPASSWD: ALL
The changes should appear as follows:
## Allows people in group wheel to run all commands # %wheel ALL=(ALL) ALL ## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
Save the changes to the
/etc/sudoersfile.Log out and log on to the host again using the user account that you provide to NetBackup Snapshot Manager.
Run the following command to confirm that the changes are in effect:
# sudo su
If you do not see any prompt requesting for a password, then the user account has been granted password-less sudo access.
You can now proceed to configure the NetBackup Snapshot Manager agentless feature.
Install and enable OpenSSH Server on the Windows VM.
For a complete procedure to install OpenSSH server on Windows and start the service, refer to Microsoft Documentation.
Enable port 22 from the security group and firewall for the Windows VMs.
Port 22 is enabled by default once the OpenSSH server is installed and enabled in the above step.
Powershell version 5.1 or later must be installed.
(Optional) If user had enabled WMI/SMB ports and they are not used by any other application, you can disable these ports from the security groups and the firewall rules after upgrading to NetBackup Snapshot Manager version 10.4.
Note:
The agentless feature is supported for Microsoft Windows version 2019 and above.
Hosts with Windows OS are not supported in OCI for agentless and on host agents.