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. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Cloud Scale Disaster Recovery
  5. Cluster backup
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Cluster backup

AKS cluster

Once NetBackup is up and running and the basic sanity test is done to ensure that the cluster is in a working state, then save the template of the cluster through CLI as follows:

  • Ensure that you are logged in through Azure CLI with subscription set to where the cluster is present:

    az group export --resource-group <resource_group> --resource-ids <resourceID> --include-parameter-default-value

    Or

    az group export --resource-group <resource_group> --resource-ids /subscriptions/${subscription_id}/resourceGroups/$resource_group/providers/Microsoft.ContainerService/managedClusters/$cluster_name --include-parameter-default-value

    Here,

    Parameter

    Description

    resource_group

    Resource group where the cluster is present.

    resourceID

    Cluster's resource ID. This can be obtained from the azure portal by navigating to the cluster and clicking on the JSON link present on the top corner of the Overview.

    subscription_id

    Subscription ID where cluster is present.

    cluster_name

    Cluster name that needs to be saved.

  1. Copy the JSON output to a file and save it as a JSON file. For example, template.json

  2. Ensure that template.json file is saved and is safe. This is required later to recover the cluster.

  3. Note the Azure Container Registry name which is attached to the cluster.

EKS cluster

Note:

User must save the output of every command in different file.

  1. Get the cluster details.

    • Use the following command to obtain the information of the cluster:

      aws eks describe-cluster --name <cluster name>

    • Obtain the detailed information about each subnet which was received as output of the above command:

      aws ec2 describe-subnets --subnet-ids <subnetID-1> <subnetID-2>

    • Obtain the IAM role name from describe-cluster command and using the following command save the policies attached to it:

      aws iam list-attached-role-policies --role-name <role name>

    • Obtain the security group ID from describe-cluster command and using following command save the details of security-groups:

      aws ec2 describe-security-groups --group-ids <Security group ID>

  2. Get the nodegroup details.

    • Use the following command to get the list of all node groups:

      aws eks list-nodegroups --cluster-name <cluster-name>

    • Obtain the information of a particular nodegroup from above list using the following command:

      aws eks describe-nodegroup --nodegroup-name <nodegroup-name> --cluster-name <cluster-name>

      User must execute this command for each node group in the cluster to obtain the details of each nodegroup.

  3. Get the EFS ID details.

    NetBackup uses two EFS IDs (Primary and Snapshot Manager server):

    Get EFS ID of Primary server: spec > primary > storage > catalog > storageClassName

    Get EFS ID of Snapshot Manager server: Get storage class name from spec > cpserver > storage > log > storageClassName.

    Describe this storage class using the following command and note the fileSystemId:

    kubectl describe sc storageClassName

    Use following commands to describe EFS:

    aws efs describe-file-systems --file-system-id <EFS ID>

    Run the above EFS command for Primary and Snapshot Manager server EFS ID. The above EFS command does not describe the mount targets which was used while creating EFS. To get mount targets details use the following command:

    aws efs describe-mount-targets --file-system-id <EFS ID>

    Note the non-default parameters with which EFS was created.

  4. Get the list of Add-on by using the following command:

    aws eks list-addons --cluster-name <cluster-name>

Feedback

Was this page helpful?
Previous

Cloud Scale Disaster Recovery

Next

Environment backup

Feedback

Was this page helpful?