CSNAPC-9769: SCO backup verification leaves stale export policies on ONTAP
Issue
SCO backup with verification is successful but leaves behind stale export policies on ONTAP once the clone is deleted after verification completes.
This is observed for a specific configuration in NFS filesystem where user mounts directly BOTH the volume AND its sub directories on a linux host.
We were able to reproduce the issue in-house by changing the mount configs
Example repro config:
- Data vol svm21/datavol is mounted on /mnt/data on the linux host
- Create a new directory under datavol(eg- TB1) and mount TB1 directory directly on host under /mnt/TB1
- svm21/datavol ------- /mnt/data
- svm21/datavol/TB1 ------- /mnt/TB1
- create a new tablespace on /mnt/TB1 and register the same to the database
- Take a new backup with verification of the database from SC
- Backup with verification completes successfully leaving behind one SC generated Export Policy in ONTAP(1 export policy per extra mount)