NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Last Published:
Product(s): NetBackup & Alta Data Protection (10.1)
  1. Introduction to NetBackup on EKS
    1.  
      About NetBackup deployment on Amazon Elastic Kubernetes (EKS) cluster
    2.  
      Required terminology
    3.  
      User roles and permissions
    4.  
      About MSDP Scaleout
    5.  
      About MSDP Scaleout components
    6.  
      Limitations in MSDP Scaleout
  2. Deployment with environment operators
    1. About deployment with the environment operator
      1.  
        Prerequisites
      2.  
        Contents of the TAR file
      3.  
        Known limitations
    2.  
      Deploying the operators manually
    3.  
      Deploying NetBackup and MSDP Scaleout manually
    4.  
      Configuring the environment.yaml file
    5.  
      Uninstalling NetBackup environment and the operators
    6.  
      Applying security patches
  3. Assessing cluster configuration before deployment
    1.  
      How does the webhook validation works
    2.  
      Webhooks validation execution details
    3.  
      How does the Config-Checker utility work
    4.  
      Config-Checker execution and status details
  4. Deploying NetBackup
    1.  
      Preparing the environment for NetBackup installation on EKS
    2.  
      Recommendations of NetBackup deployment on EKS
    3.  
      Limitations of NetBackup deployment on EKS
    4. About primary server CR and media server CR
      1.  
        After installing primary server CR
      2.  
        After Installing the media server CR
    5.  
      Monitoring the status of the CRs
    6.  
      Updating the CRs
    7.  
      Deleting the CRs
    8.  
      Configuring NetBackup IT Analytics for NetBackup deployment
    9.  
      Managing NetBackup deployment using VxUpdate
    10.  
      Migrating the node group for primary or media servers
  5. Upgrading NetBackup
    1.  
      Preparing for NetBackup upgrade
    2.  
      Upgrading NetBackup operator
    3.  
      Upgrading NetBackup application
    4.  
      Upgrade NetBackup during data migration
    5.  
      Procedure to rollback when upgrade fails
  6. Deploying MSDP Scaleout
    1.  
      Deploying MSDP Scaleout
    2.  
      Prerequisites
    3.  
      Installing the docker images and binaries
    4.  
      Initializing the MSDP operator
    5.  
      Configuring MSDP Scaleout
    6.  
      Using MSDP Scaleout as a single storage pool in NetBackup
    7.  
      Configuring the MSDP cloud in MSDP Scaleout
  7. Upgrading MSDP Scaleout
    1.  
      Upgrading MSDP Scaleout
  8. Monitoring NetBackup
    1.  
      Monitoring the application health
    2.  
      Telemetry reporting
    3.  
      About NetBackup operator logs
    4.  
      Expanding storage volumes
    5.  
      Allocating static PV for Primary and Media pods
  9. Monitoring MSDP Scaleout
    1.  
      About MSDP Scaleout status and events
    2.  
      Monitoring with Amazon CloudWatch
    3.  
      The Kubernetes resources for MSDP Scaleout and MSDP operator
  10. Managing the Load Balancer service
    1.  
      About the Load Balancer service
    2.  
      Notes for Load Balancer service
    3.  
      Opening the ports from the Load Balancer service
  11. Performing catalog backup and recovery
    1.  
      Backing up a catalog
    2.  
      Restoring a catalog
  12. Managing MSDP Scaleout
    1.  
      Adding MSDP engines
    2.  
      Adding data volumes
    3. Expanding existing data or catalog volumes
      1.  
        Manual storage expansion
    4.  
      MSDP Scaleout scaling recommendations
    5. MSDP Cloud backup and disaster recovery
      1.  
        About the reserved storage space
      2.  
        Cloud LSU disaster recovery
    6.  
      MSDP multi-domain support
    7.  
      Configuring Auto Image Replication
    8. About MSDP Scaleout logging and troubleshooting
      1.  
        Collecting the logs and the inspection information
  13. About MSDP Scaleout maintenance
    1.  
      Pausing the MSDP Scaleout operator for maintenance
    2.  
      Logging in to the pods
    3.  
      Reinstalling MSDP Scaleout operator
    4.  
      Migrating the MSDP Scaleout to another node group
  14. Uninstalling MSDP Scaleout from EKS
    1.  
      Cleaning up MSDP Scaleout
    2.  
      Cleaning up the MSDP Scaleout operator
  15. Troubleshooting
    1.  
      View the list of operator resources
    2.  
      View the list of product resources
    3.  
      View operator logs
    4.  
      View primary logs
    5.  
      Pod restart failure due to liveness probe time-out
    6.  
      Socket connection failure
    7.  
      Resolving an invalid license key issue
    8.  
      Resolving an issue where external IP address is not assigned to a NetBackup server's load balancer services
    9.  
      Resolving the issue where the NetBackup server pod is not scheduled for long time
    10.  
      Resolving an issue where the Storage class does not exist
    11.  
      Resolving an issue where the primary server or media server deployment does not proceed
    12.  
      Resolving an issue of failed probes
    13.  
      Resolving token issues
    14.  
      Resolving an issue related to insufficient storage
    15.  
      Resolving an issue related to invalid nodepool
    16.  
      Resolving a token expiry issue
    17.  
      Resolve an issue related to KMS database
    18.  
      Resolve an issue related to pulling an image from the container registry
    19.  
      Resolving an issue related to recovery of data
    20.  
      Check primary server status
    21.  
      Pod status field shows as pending
    22.  
      Ensure that the container is running the patched image
    23.  
      Getting EEB information from an image, a running container, or persistent data
    24.  
      Resolving the certificate error issue in NetBackup operator pod logs
    25.  
      Resolving the primary server connection issue
    26.  
      Primary pod is in pending state for a long duration
    27.  
      Host mapping conflict in NetBackup
    28.  
      NetBackup messaging queue broker take more time to start
    29.  
      Local connection is getting treated as insecure connection
    30.  
      Issue with capacity licensing reporting which takes longer time
    31.  
      Backing up data from Primary server's /mnt/nbdata/ directory fails with primary server as a client
  16. Appendix A. CR template
    1.  
      Secret
    2.  
      MSDP Scaleout CR

Monitoring with Amazon CloudWatch

You can use Amazon CloudWatch to collect Prometheus metrics to monitor pods in MSDP-X cluster.

To configure Amazon CloudWatch

  1. Install the CloudWatch agent with Prometheus metrics collection on EKS.

    See AWS documentation.

  2. Install the CloudWatch agent on EKS clusters. Select the EC2 launch type, and download the template YAML file Prometheus-eks.yaml.
  3. Add the YAML file with the following sample configuration.
    # create configmap for prometheus cwagent config
    apiVersion: v1
    data:
      # cwagent json config
      cwagentconfig.json: |
        {
          "logs": {
            "metrics_collected": {
              "prometheus": {
                "prometheus_config_path": "/etc/prometheusconfig/
                 prometheus.yaml",
                "emf_processor": {
                  "metric_declaration": [
                    {
                      "source_labels": ["job"],
                      "label_matcher": "^msdpoperator-metrics",
                      "dimensions":[
                        ["ClusterName","NameSpace"]
                      ],
                      "metric_selectors": [
                        "msdpoperator_reconcile_failed",
                        "msdpoperator_operator_run",
                        "msdpoperator_diskFreeLess5GBEngines_total",
                        "msdpoperator_diskFreeMiBytesInEngine",
                        "msdpoperator_diskFreeLess10GBClusters_total",
                        "msdpoperator_totalDiskFreePercentInCluster",
                        "msdpoperator_diskFreePercentInEngine",
                        "msdpoperator_pvcFreePercentInCluster",
                        "msdpoperator_unhealthyEngines_total",
                        "msdpoperator_createdPods_total"
                      ]
                    }
                  ]
                }
              }
            },
            "force_flush_interval": 5
          }
        }
    kind: ConfigMap
    metadata:
      name: prometheus-cwagentconfig
      namespace: amazon-cloudwatch
     
    ---
    # create configmap for prometheus scrape config
    apiVersion: v1
    data:
      # prometheus config
      prometheus.yaml: |
        global:
          scrape_interval: 1m
          scrape_timeout: 10s
        scrape_configs:
        - job_name: 'msdpoperator-metrics'
     
          scheme: https
          tls_config:
            ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
            insecure_skip_verify: true
          bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount
          /token
     
          kubernetes_sd_configs:
          - role: pod
     
          relabel_configs:
          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io
            _scrape]
            action: keep
            regex: true
          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io
            _path]
            action: replace
            target_label: __metrics_path__
            regex: (.+)
          - source_labels: [__address__, __meta_kubernetes_pod_annotation_
            prometheus_io_port]
            action: replace
            regex: ([^:]+)(?::\d+)?;(\d+)
            replacement: $1:$2
            target_label: __address__
          - source_labels: [__meta_kubernetes_namespace]
            action: replace
            target_label: NameSpace
          - source_labels: [__meta_kubernetes_pod_name]
            action: replace
            target_label: PodName
     
    kind: ConfigMap
    metadata:
      name: prometheus-config
      namespace: amazon-cloudwatch
    

    Table: Supported Prometheus metrics list in MSDP Scaleout lists the Prometheus metrics that MSDP Scaleout supports.

  4. Apply the YAML file.

    Kubectl apply -f Prometheus-eks.yaml

    The default log groups name is /aws/containerinsights/{cluster_name}/Prometheus.

  5. Create Amazon CloudWatch alarms.

    See Using Amazon CloudWatch alarms in AWS documentation.

  6. In the CloudWatch console, add the related log query. In the navigation pane, select Log Insights.

    For example, the free space size of the MSDP scaleout cluster engines is lower than 1 GB in past 5 minutes. Select the log group from the drop-down list, and select the time duration 5m on the time line.

    Log query:

    fields @timestamp, @message
    | filter msdpoperator_diskFreeMiBytesInEngine <= 100000
    | sort @timestamp desc
    

    If multiple MSDP scaleout clusters are deployed in the same EKS cluster, use the filter to search the results. For example, search the MSDP engines with the free space size lower than 1GB in the namespace sample-cr-namespace.

    Log query:

    fields @timestamp, @message
    | filter msdpscalout_ns == "sample-cr-namespace"
    | filter msdpoperator_diskFreeMiBytesInEngine <= 100000
    | sort @timestamp desc
    

MSDP Scaleout supports the following Prometheus metrics:

Table: Supported Prometheus metrics list in MSDP Scaleout

Metrics

Type

Filters

Description

msdpoperator_reconcile_total

Counter

N/A

The total of the reconcile loops msdp-operator run.

msdpoperator_reconcile_failed

Counter

N/A

The total of the reconcile loops msdp-operator failed to run.

msdpoperator_operator_run

Counter

N/A

The total of the running operator.

msdpoperator_diskFree Less5GBEngines_total

Gauge

msdpscalout_ns

The checked number of the engines which have free spaces lower than 5GB.

msdpoperator_diskFree MiBytesInEngine

Gauge

msdpscalout_ns

The free space of current engine in MiBytes.

msdpoperator_diskFreeLess 10GBClusters_total

Gauge

msdpscalout_ns

The checked number of the msdpscaleout applications that have free spaces lower than 10GB.

msdpoperator_totalDiskFree PercentInCluster

Gauge

msdpscalout_ns

The percent of the msdpscaleout applications that have free spaces. For example, 0.95 means 95%

msdpoperator_diskFree PercentInEngine

Gauge

msdpscalout_ns

The percent of the current engines, which have free spaces.

msdpoperator_pvcFree PercentInCluster

Gauge

msdpscalout_ns, component

The percent of the used PVC, which have free spaces.

msdpoperator_unhealthy Engines_total

Gauge

msdpscalout_ns

The total of unhealthy engines.

msdopoerator_createdPods_total

Gauge

msdpscalout_ns, component

The total of created msdpscaleout pods.