Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
  3. Section I. NetBackup Snapshot Manager for Cloud installation and configuration
  4. Deploying NetBackup Snapshot Manager for Cloud extensions
  5. Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
  6. Installing the extension on AWS (EKS)
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

Installing the extension on AWS (EKS)

Before you install the NetBackup Snapshot Manager extension:

  • See Prerequisites to install the extension on a managed Kubernetes cluster in AWS.

  • See Downloading the NetBackup Snapshot Manager extension.

To install the extension

  1. 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.

  2. 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

  3. 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: 11.1.x.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:11.1.x.x-xxxx
        <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-deploy:11.1.x.x-xxxx
        docker tag veritas/flexsnap-core:11.1.x.x-xxxx
        <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-core:11.1.x.x-xxxx
        docker tag veritas/flexsnap-fluentd:11.1.x.x-xxxx 
        <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-fluentd:11.1.x.x-xxxx
        docker tag veritas/flexsnap-datamover:11.1.x.x-xxxx
        <account_id>.dkr.ecr.us-east-2.amazonaws.com/veritas/flexsnap-datamover:11.1.x.x-xxxx
  4. 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:11.1.x.x-xxxx
    docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/
    flexsnap-deploy:11.1.x.x-xxxx
    docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/
    flexsnap-fluentd:11.1.x.x-xxxx
    docker push <account-id>.dkr.ecr.us-east-2.amazonaws.com/veritas/
    flexsnap-core:11.1.x.x-xxxx
    

    Note:

    The command/output examples may be formatted or truncated to fit the screen.

  5. 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 and cloudpoint_crd.yaml files based on the samples provided.

      See Install extension using the Kustomize and CR YAMLs.

    • 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.

      See Install extension using the extension script.

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 and go to NetBackup Snapshot Manager extensions tab and verify.

  • Run the following command and verify that there are four pods, namely, flexsnap-deploy-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxx and flexsnap-fluentd-collector-xxx are in Running state:

    # kubectl get pods -n <namespace>

    Example: # kubectl get pods -n cloudpoint-system

Feedback

Was this page helpful?
Previous

Prerequisites to install the extension on a managed Kubernetes cluster in AWS

Next

Install extension using the extension script

Feedback

Was this page helpful?