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
Installing the extension on AWS (EKS)
Before you install the NetBackup Snapshot Manager extension:
To install the extension
- The extension file
nbu_flexsnap_extension.tar
must be downloaded beforehand.See Downloading the NetBackup Snapshot Manager extension.
Note:
Do not create the authentication token yet, as it is valid only for 180 seconds.
- If the host from which you want to install the extension is not the same host where your NetBackup Snapshot Manager is installed, load the NetBackup Snapshot Manager container images on the extension host (
flexsnap-deploy, flexsnap-core, flexsnap-fluentd, flexsnap-datamover
)The image names are in the following format:
Example:
veritas/flexsnap-deploy
- Create image tags to map the source image with the target image, so that you can push the images to the AWS container registry.
See Prerequisites to install the extension on a managed Kubernetes cluster in AWS.
Gather the following parameters beforehand:
Parameter
Description
container_registry_path
To obtain the container registry path, go to your Amazon ECR and copy the URI of each repo.
Example: <accoint_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-datamover
tag
NetBackup Snapshot Manager image version.
Example:
10.2.x.xxxx
To tag the images, run the following command for each image, depending on the container platform running on your host:
For Docker: # docker tag source_image:tag target_image:tag
For Podman: # podman tag source_image:tag target_image:tag
Where,
the source image tag is: veritas/flexsnap-deploy:tag>
the target image tag is: <container_registry_path>/<source_image_name>:<SnapshotManager_version_tag>
Example:
docker tag veritas/flexsnap-deploy:10.2.x.xxxx <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-deploy:10.2.x.xxxx docker tag veritas/flexsnap-core:10.2.x.xxxx <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-core:10.2.x.xxxx docker tag veritas/flexsnap-fluentd:10.2.x.xxxx <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-fluentd:10.2.x.xxxx docker tag veritas/flexsnap-datamover:10.2.x.xxxx <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-datamover:10.2.x.xxxx
- Then to push the images to the container registry, run the following command for each image, depending on the container platform running on your host:
For Docker: # docker push target_image:tag
For Podman: # podman push target_image:tag
Example:
docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/ flexsnap-datamover:10.2.x.xxxx docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/ flexsnap-deploy:10.2.x.xxxx docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/ flexsnap-fluentd:10.2.x.xxxx docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/ flexsnap-core:10.2.x.xxxx
Note:
The command/output examples may be formatted or truncated to fit the screen.
- Once the images are pushed to the container registry, you can install the extension using one of the following methods:
Kustomization and custom resource YAML files: Create and apply the
kustomization.yaml
andcloudpoint_crd.yaml
files based on the samples provided.Extension script: Execute the extension script
cp_extension.sh
that is packaged within the 'tar' file that was downloaded earlier. The script can be executed either by providing all the required input parameters in one command, or in an interactive way where you will be prompted for input.
After following the above instructions, you can verify if the extension was installed successfully.
To verify that the extension is installed successfully:
Verify that the success message is displayed at the command prompt.
Verify that the extension is listed on the NetBackup Web UI.
Navigate to Cloud > NetBackup Snapshot Manager tab > click Advanced settings > go to NetBackup Snapshot Manager extensions tab and verify.
Run the following command and verify that there are five pods, namely,
flexsnap-cloudpoint-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxx, flexsnap-fluentd-collector-xxx
andflexsnap-datamover-xxxx
are in Running state:# kubectl get pods -n <namespace>
Example: # kubectl get pods -n cloudpoint-system