How Data-Migration works

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 disks to Azure premium files for 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 files for 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 disk catalog 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 files storage class must be provided in the environment.yaml file 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 in environment.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.