Data migration unsuccessful even after changing the storage class through the storage yaml file
To resolve the data migration unsuccessful issue
- Check if the previous/older migration PVC is still present.
- Check if an existing migration job is in pending/running state.
- Migration will not be triggered if storage class name is not changed for volumes (catalog) of primary server.
- Check if the updated storage yaml file is set to use any other storage class other than
Azure premium filesfor catalog. - Check if the protocol version for catalog storage class is set to NFS to allow successful migration.
- Check if the status of migration reported by the migration pod in the logs is other than MigrationStatus: Passed.
- Ensure that the User's Azure subscription has Classic Network Contributor role which is also a pre-requisite for migration/upgrade.
Note:
If reconciler is called while migration PVC exists the invocation will be failed, customers must wait for the completion of a migration job if an existing migration job is running and they can also monitor the migration job pods to check if there are any issues with the migration job. In order to resolve any problems encountered during existing migration job pod they may choose to delete the migration job pod manually. If the migration job pod does not exist, then customer may delete the migration PVC.