NetBackup™ Marketplace Deployment on Amazon Elastic Kubernetes Service (EKS) Cluster

Last Published:
Product(s): NetBackup & Alta Data Protection (10.2)

Accessing the NetBackup after deployment

Once the operators are created successfully, CloudFormation will display deployment as successful. To verify the NetBackup installation status, connect to the cluster and check the status.

After the deployment is successful, perform the below steps to access the NetBackup.

  1. Create an EC2 instance to access EKS cluster. Provide the IAM role created to access EKS Cluster to this EC2 instances. Ensure that these EC2 instances have following:

    • It must have Linux operating system.

    • It must have Docker daemon, Kubernetes command-line tool (kubectl), and AWS CLI installed.

  2. Login to the AWS environment to access the Kubernetes cluster by running the following command on AWS CLI:

    aws eks --region <region_name> update-kubeconfig --name <cluster_name>

  3. Execute the command:

    kubectl get namespaces.

    After executing the above command, you will get list of namespaces created. You can also view by navigating through UI under Kubernetes resources.

  4. To view the MSDP and NetBackup Operators, execute the below command: :

    kubectl get all --namespace netbackup-operator-system

  5. To view the NetBackup deployment environment, execute the below command. Verify that all the resources are up and running successfully.

    kubectl get --namespace <deployment namespace> all,environments, primaryservers, mediaservers, msdpscaleouts, cpservers

    Output:

    All pod status should be Ready and Running
NAME                            	READY     STATUS
pod/<environment-     													1/1    Running
name>-primary-0
    Overall application environment status:
NAME 						                      READY   AGE   STATUS
environemnt.netbackup.													4     27h   Success
<environment-name>
    Primary server status:
NAME 									                   TAG     	AGE  PRIMARY SERVER   STATUS
primaryserver.netbackup.    				10.2      27h  <primary server  Success
veritas.com/<environment-name>                                   fqdn>
Media server status:
NAME 						                      TAG      AGE   STATUS
mediaserver.netbackup.											10.2    26h   Success
.veritas.com/<environment-name>
    Storage server status:
NAME 									                   TAG     	AGE  SIZE   READY
msdpcscaleout.msdp.veritas.com/  18.0     27h    4      4
.veritas.com/<environment-name>                                  
Media server status:
NAME 						                      READY   AGE   STATUS
environemnt.netbackup.													4     27h   Success
<environment-name>
    Snapshot Manager server status:
NAME																													TAG				        AGE			STATUS				
cpserver.netbackup					         10.2.0.0.1034		 146m  Success	
.veritas.com/<environment-name>

  6. Access the NetBackup Web UI using link.

    Note:

    The primaryserver is the host name or IP address of the NetBackup primary server that you want to sign in to.

    To get the primary server hostname you may use the following command and check the hostname under the Primary Server Details section:

    kubectl describe primaryserver.netbackup.veritas.com/<name of primaryserver custom resource>

  7. From the Web UI under the Storage Configuration > Storage servers, you can see the storage server configuration details.

    Note:

    By default, you will not have permission to view cluster resource status on AWS EKS UI. If you want to monitor status of resources, add IAM users or roles to your Amazon EKS cluster. For more details refer Enabling IAM user and role access to your cluster

  8. The proxy settings for Snapshot Manager are not enabled by default. If you want to enable them, follow below given steps:

  • Uninstall Snapshot Manager from EKS by deleting the CPServer related parameters from environment.yaml file. Make sure to keep copy of CPServer related parameters. Run the below command to edit the environment.yaml

  • kubectl edit environment <environment_name> -n netbackup

  • Ensure that you get the uninstall message in flexsnap-operator operator log.

  • Once Snapshot Manager is uninstalled successfully, add CPServer related parameters to the environment.yaml again with proxy settings as below:

    proxySettings:

    # Represents the value to be used as the HTTP proxy for all connections.

    vx_http_proxy: "http://proxy.mycompany.com:8080/"

    # Represents the value to be used as the HTTPS proxy for all connections.

    vx_https_proxy: "https://proxy.mycompany.com:8080/"

    # Represents the addresses that are allowed to bypass the proxy server. You can specify host names, IP addresses, and domain names in this parameter.

    vx_no_proxy: "localhost,mycompany.com,192.168.0.10:80"