Operational Defect Database
BugZero found this defect 291 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4480
Unexpected Snapshot Deletion Failures in the Job Sessions for ONTAP 9.13.1
Last update date:
1/31/2024
Affected products:
Veeam Backup & Replication
Affected releases:
11
Fixed releases:
No fixed releases provided.
Description:
Challenge
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
Cause
Due to a change starting in ONTAP 9.13.1, cloned volumes fall into the recovery queue for 12 hours by default. The parent snapshot receives a 'busy' state and cannot be deleted before the clone leaves the queue and is removed completely from storage. 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.
Solution
This issue was resolved starting in Veeam Backup & Replication 12.1.
More Information
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.
