Check the migration pod logs for details using the following command:

kubectl logs <catalog-or-log-migration-job-name> -n <netbackup-environment-namespace>

Manually copy or ignore the files or continue with the next steps.

Save the PVC's volume name and storage class as follows:

kubectl describe pvc <azure-disk- or-files-pvc-name> 
-n <netbackup-environment-namespace>

Delete the old Azure disk or files PVC, and rename the new Azure files PVC to the old Azure disk or files PVC name as follows:

kubectl delete pvc <azure-disk-or-files-pvc-name> 
-n <netbackup-environment-namespace>
kubectl patch pv <saved_volume_name> --type json 
-p '[{"op": "remove", "path": "/spec/claimRef"}]'

Ensure that the PV is available after completing the previous steps.

Create a new Azure files PVC with the old PV as follows:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: <old_pvc_name>
  namespace: <old_pvc_namespace>
spec:
  accessModes:
    - ReadWriteMany
  volumeName: <saved_volume_name>
  storageClassName: <saved_storage_class_name>
  resources:
    requests:
      storage: 100Gi #previous files size

Enable the probes /opt/veritas/vxapp-manage/nb-health enable.

Set replica count to 1 or reapply environment.yaml file as follows:

kubectl scale --replicas=1 <STS name> -n <netbackup-environment-namespace> or reapply the environment.yaml file.