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™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster
  3. Assessing cluster configuration before deployment
  4. Data-Migration execution and status details
NetBackup™ Deployment Guide for Azure Kubernetes Services (AKS) Cluster

Data-Migration execution and status details

Data migration is carried out in form of job in NetBackup Kubernetes cluster for only the primary server CR. There will be a migration job per primary volume for data migration which will be part of NetBackup environment namespace. Each job creates a pod in the cluster.

  • Execution summary of the Data migration can be retrieved from the migration pod logs using the following command:

    kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>

    This summary can also be retrieved from the operator pod logs using the following command:

    kubectl logs <netbackup-operator-pod-name> -n <netbackup-environment-namespace>

  • Status of the data migration can be retrieved from the primary server CR by using the following command:

    kubectl describe <PrimaryServer> <CR name> -n <netbackup-environment-namespace>

    Following are the data migration statuses:

    • Success: Indicates all necessary conditions for the migration of the Primary server are passed.

    • Failed: Indicates some or all necessary conditions for the migration the Primary server are failed.

    • Running: Indicates migration is in running state for the Primary server.

  • If the Data migration execution status is failed, you can check the migration job logs using the following command:

    kubectl logs <migration-pod-name> -n <netbackup-environment-namespace>

    Review the error codes and error messages pertaining to the failure and update the primary server CR with the correct configuration details to resolve the errors.

    For more information about the error codes, refer to NetBackup™ Status Codes Reference Guide.

Feedback

Was this page helpful?
Previous

How Data-Migration works

Next

Deploying NetBackup

Feedback

Was this page helpful?