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 to install the extension on a managed Kubernetes cluster in AWS
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.
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.
Install a Docker or Podman container platform on the host and start the container service.
It is not recommended to change scale settings of the cluster nodegroup when jobs are running. Disable the extension when jobs are not running, then change the scale settings and enable the extension for new jobs.
Prepare the NetBackup Snapshot Manager host to access Kubernetes cluster within your AWS environment.
Install AWS CLI. For more information, refer to the AWS Command Line Interface.
Install Kubernetes CLI. For more information, refer to the Installing kubectl documentation.
Create an AWS Container Registry or use the existing one if available, to which the NetBackup Snapshot Manager images will be pushed (uploaded). Configure the minimum and maximum nodes as per the requirement.
For more information, refer to the AWS documentation Amazon Elastic Container Registry documentation.
Create the OIDC provider for the AWS EKS cluster. For more information, refer to the Create an IAM OIDC provider for your cluster section of the Amazon EKS User Guide.
Create an IAM service account for the AWS EKS cluster. For more information, refer to the Amazon EKS User Guide.
If an IAM role needs an access to the EKS cluster, run the following command from the system that already has access to the EKS cluster:
kubectl edit -n kube-system configmap/aws-auth
For more information, refer to the Enabling IAM user and role access to your cluster section of the Amazon EKS User Guide.
Install Amazon EFS driver. For more information, refer to the Amazon EFS CSI driver section of the Amazon EKS User Guide.
Login to the AWS environment to access the Kubernetes cluster by running this command on AWS CLI:
# aws eks --region <region_name> update-kubeconfig --name <cluster_name>
Create a storage class. For more information, refer to the Storage classes section of the Amazon EKS User Guide.
Create a namespace for NetBackup Snapshot Manager from the command line on host system:
# kubectl create namespace cloudpoint-system
Then create a new or use an existing managed Kubernetes cluster in AWS, and add a new node pool dedicated for NetBackup Snapshot Manager use. Configure Autoscaling as per your requirement.
While defining StorageClass, set
uid/gid
to the root.Following is an example for StorageClass:
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: efs-sc1 parameters: basePath: /dynamic_provisioning_bhakti directoryPerms: "700" fileSystemId: fs-03e18dc283779991e gid: "0" provisioningMode: efs-ap uid: "0" provisioner: efs.csi.aws.com reclaimPolicy: Delete volumeBindingMode: Immediate