Snapshots created by Commvault Intellisnap are not saved on a volume
This knowledge base was generated through a script and may contain formatting issues. For the accurate content, please refer to the WIP editor. WIP editor.
Applies to
- ONTAP 9
- Snapshot
- Commvault Intellisnap
Issue
- Snapshot created by Commvault Intellisnap are not saved on a volume.
- The creation of snapshot has been confirmed on Commvault side
- The creation of the snapshot are confirmed on
AUDIT-MLOG
:
Wed May 29 2024 21:00:22 +02:00 [kern_audit:info:3065] 8503e90000027980 ::
cluster:ontapi :: x.x.x.x:xx :: SVM1:vsadmin ::
nmsdk_platform="Windows Server 2022 Datacenter AMD64" version="1.7"
xmlns="http://www.netapp.com/filer/admin"
nmsdk_version="9.8">snapshotImpacted
Vol1
IntelliSnap
:: Pending:
Wed May 29 2024 21:00:22 +02:00 [kern_audit:info:3065] 8503e90000027980 ::
cluster:ontapi :: x.x.x.x:xx :: SVM1:vsadmin :: snapshot-create :: Success:
- At the same time of Snapshot creation,
EMS.log
shows autodeletion of Snapshot:
Wed May 29 21:00:22 +0200 [cluster-02: snap_helper:
wafl.volume.snap.autoDelete:info]: Deleting Snapshot copy 'snapshotImpacted' in
volume 'Vol1@vserver:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx' to recover storage.
Volume details
show:
VOLUME : Space Reserved for Snapshot Copies : 0%
VOL-STATUS-V
shows:
Snapshot autodelete settings: state=on, commitment=try, trigger=snap_reserve, target_free_space=20%,