Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- CloudPoint host sizing recommendations
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Installing the CloudPoint extension on AWS (EKS)
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
- Nutanix Files plug-in configuration notes
- Dell EMC Unity array plug-in configuration notes
- FUJITSU AF/DX plug-in configuration notes
- NetApp NAS plug-in configuration notes
- Dell EMC PowerStore plug-in configuration notes
- Dell EMC PowerStore NAS plug-in configuration notes
- Dell EMC PowerFlex plug-in configuration notes
- Dell EMC XtremIO SAN plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- Pure Storage FlashBlade plug-in configuration notes
- IBM Storwize plug-in configuration notes
- HPE RMC plug-in configuration notes
- HPE XP plug-in configuration notes
- Hitachi plug-in configuration notes
- Hitachi (HDS VSP 5000) plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Dell EMC PowerMax and VMax plug-in configuration notes
- Qumulo plug-in configuration notes
- CloudPoint application agents and plug-ins
- Oracle plug-in configuration notes
- Additional steps required after a SQL Server snapshot restore
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup CloudPoint
- CloudPoint security
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Troubleshooting CloudPoint
Installing the CloudPoint extension on AWS (EKS)
Before you install the CloudPoint extension:
To install the extension
- The extension file
nbu_cloudpoint_extension.tar
must be downloaded beforehand.See Downloading the CloudPoint 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 CloudPoint is installed, load the CloudPoint container images on the extension host (
flexsnap-cloudpoint, flexsnap-listener, flexsnap-workflow, flexsnap-fluentd, flexsnap-datamover
)The image names are in the following format:
Example:
veritas/flexsnap-cloudpoint
- 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 Preparing to install the extension on a managed Kubernetes cluster (EKS) 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
CloudPoint image version.
Example:
10.2.0.9129
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-cloudpoint:tag>
the target image tag is: <container_registry_path>/<source_image_name>:<CloudPoint_version_tag>
Example:
docker tag veritas/flexsnap-cloudpoint:10.2.0.9129 <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-cloudpoint:10.2.0.9129 docker tag veritas/flexsnap-listener:10.2.0.9129 <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-listener:10.2.0.9129 docker tag veritas/flexsnap-fluentd:10.2.0.9129 <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-fluentd:10.2.0.9129 docker tag veritas/flexsnap-workflow:10.2.0.9129 <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-workflow:10.2.0.9129 docker tag veritas/flexsnap-datamover:10.2.0.9129 <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-datamover:10.2.0.9129
- 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.0.9129 docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-cloudpoint:10.2.0.9129 docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-fluentd:10.2.0.9129 docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-listener:10.2.0.9129 docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-workflow:10.2.0.9129
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 by one of the following two ways:
Kustomization and custom resource YAML files: create and apply the
kustomize.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.
Go to Cloud > CloudPoint Servers tab > click Advanced settings > go to CloudPoint extensions tab and verify.
Run the following command and verify that there are four pods, namely,
flexsnap-cloudpoint-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxx, flexsnap-fluentd-collector-xxx, flexsnap-datamover-xxxx
in Running state:# kubectl get pods -n <namespace>
Example: # kubectl get pods -n cloudpoint-system