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
- 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
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager 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 cloud providers
- 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
- 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
- About NetBackup Snapshot Manager upgrades
- Supported upgrade path
- Upgrade scenarios
- Preparing to upgrade NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager using patch or hotfix
- Migrating and upgrading NetBackup Snapshot Manager
- GCP configuration for migration from zone to region
- Post-upgrade tasks
- Post-migration tasks
- Uninstalling NetBackup Snapshot Manager
- 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
- 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 from snapshot job fails with timeout error
Prerequisites to install the extension on a managed Kubernetes cluster in Azure
Choose the NetBackup Snapshot Manager image supported on Ubuntu or RHEL system that meets the NetBackup Snapshot Manager installation requirements and create a host.
See Creating an instance or preparing the host to install NetBackup Snapshot Manager.
It is not recommended to scale the cluster up or down when a job is running. It might cause the job to fail. Set the cluster size beforehand.
Verify that the port 5671 is open on the main NetBackup Snapshot Manager host.
See Verifying that specific ports are open on the instance or physical host.
The public IP of the virtual machine scale set via which the node pool is configured has to be allowed to communicate through port 22, on the workloads being protected.
Install a Docker or Podman container platform on the host and start the container service.
Prepare the NetBackup Snapshot Manager host to access Kubernetes cluster within your Azure environment.
Install Azure CLI. For more information, refer to the Azure documentation.
Install Kubernetes CLI. For more information, refer to the Kubernetes site.
Login to the Azure environment to access the Kubernetes cluster by running this command on Azure CLI:
# az login --identity
# az account set --subscription <subscriptionID>
# az aks get-credentials --resource-group <resource_group_name> --name <cluster_name>
Ensure that you create an Azure Container Registry or use the existing one if available, to which the NetBackup Snapshot Manager images will be pushed (uploaded). See Azure documentation.
To run the kubectl and container registry commands from the host system, assign the following role permissions to your VM and cluster. You can assign a 'Contributor', 'Owner', or any custom role that grants full access to manage all resources.
Navigate to your Virtual Machine > click Identity on the left > under System assigned tab, turn the Status to 'ON' > click Azure role assignment > click Add role assignments > select Scope as 'Subscription' or 'Resource Group' > select Role and assign the following roles : Azure Kubernetes Service RBAC Writer, AcrPush, Azure Kubernetes Service Cluster User Role, and Save.
Navigate to your Kubernetes cluster > click Access Control (IAM) on the left > click Add role assignments > select Role as 'Contributor ' > Select Assign access to as 'Virtual Machines' > select your VM from the drop-down and Save.
While defining consider using CSI provisioner for
Azure Fileswith NFS protocol.For example,
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: test-sc parameters: skuName: Premium_LRS protocol: nfs provisioner: file.csi.azure.com reclaimPolicy: Retain volumeBindingMode: WaitForFirstConsumer
Create a namespace for NetBackup Snapshot Manager from the command line interface on host system:
# kubectl create namespace cloudpoint-system
Then create a new or use an existing managed Kubernetes cluster in Azure, and add a new node pool dedicated for NetBackup Snapshot Manager use. Configure Autoscaling as per your requirement.
Ensure that Azure plug-in is configured.