OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 435 days ago.
VeeamAUX snapshots cannot be deleted immediately on ONTAP 9.13.1 or later; they are instead deleted later by tracked actions, causing cluttered logs and UI sessions. FC and iSCSI (NFS is not affected) Backup job (always) with the error: Failed to delete snapshot VeeamAUX_is_sm_1G3TRqSPOYLWmSKSVtrGBg of volume VeeamAUX_is_sm_Backup_3nPFLaxtmDioAeIzLDfLtB Details: Attempt to delete snapshot when clone is busy
Due to a change starting in ONTAP 9.13.1, cloned volumes enter the recovery queue for 12 hours by default. The parent snapshot cannot be deleted until the clone is removed from the storage and leaves the recovery queue. This change is covered in: https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1212186 When a regular flexible volume is deleted, it is placed into an ONTAP recovery queue so that it can be recovered at the later point of time before its retention time is lapsed. Unlike a regular flexible volume, when a clone volume is deleted accidentally, it is not placed into ONTAP recovery queue and as a result, recovery is not possible.
This issue was resolved starting in Veeam Backup & Replication 12.1. Starting with Veeam Backup & Replication build 12.1.0.2131, the software will check for the resulting clone volume in the recovery queue and purge it to prevent the parent snapshot removal from being blocked.
Workaround: Set the global recovery queue hours setting on the storage to zero. WARNING: This setting will impact all volumes including production ones and should be used carefully.
