Data-Migration for AKS
This section describes the working, execution and status details of the Data-Migration for AKS.
Data migration job kicks-in whenever there is any change in the storage class name of the primary server's catalog, log and data volumes.
Migration job is used to perform data transfer of Primary server's file system data from
Azure diskstoAzure premium filesfor existing NetBackup deployments.If user is deploying NetBackup for the first time, then it is considered as fresh installation and the user can directly utilize the
Azure premium filesfor Primary server's catalog volume. Primary server log and data volume supports azure disks only.For existing NetBackup deployments, migration job would copy Primary server's old
Azure diskcatalog volume to new azure file volumes, except nbdb data, nbdb data will be copied to new azure disks based data volume. Logs can be migrated to new azure disk log volume.To invoke the migration job, the
Azure premium filesstorage class must be provided in theenvironment.yamlfile for catalog volume. User can also provide new azure disks storage class for log volume and new azure disk based data volume must be provided inenvironment.yaml.The migration status is updated to Success in primary server CRD post successful data migration.
Note:
Migration will take longer time based on catalog data size.
Data migration is carried out in form of 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.