The Snaplock Expirytime is sometimes not set in ONTAP after an SCW backup
Applies to
- SnapCenter Server (SC) 5.x and above
- SnapCenter Plug-in for Microsoft Windows Server (SCW) 5.x and above
- Tamper Proof Snapshots (TPS)
Issue
- The
Snaplock-Expirytimeis sometimes not set in ONTAP. - The backup shows that SC successfully sends the
Set-NcSnapshotSnaplockExpTimebut is not applied on some snapshots in ONTAP
DEBUG SMCore_25955 PID=[6400] TID=[38] Command: Set-NcSnapshotSnaplockExpTime. Storage System: <SVM_IP>. Version: NetApp Release 9.14.1P7: Thu Aug 01 03:07:44 UTC 2024. Connection Mode: REST
DEBUG SMCore_25955 PID=[6400] TID=[38] Setting SnapshotSnaplockExpTime on volume <volume_name> and <SVM_name>
DEBUG SMCore_25955 PID=[6400] TID=[38] Set SnapLock Expiration Time: 07.10.2024 23:15:05 is successful on Volume: <volume_name>, SnapShot: <snapshot_name>
- Entries seen in ONTAP:
[kern_audit:info:3360] 8503ea00000d8272 :: NetAppRZ: http :: <SVM_IP>:52638 :: <SVM_name>:vsadmin :: PATCH /api/storage/volumes/b3e91ca2-12d5-11eb-a8ea-d039ea206f61/snapshots/196dbd30-bb4c-4c17-bde7-ba378edd36e6 : {"snaplock_expiry_time":"2024-10-07T23:15:59Z"} :: Pending
[kern_audit:info:3360] 8503ea00000d8272 :: NetAppRZ: http :: <SVM_IP>:52638 :: <SVM_name>:vsadmin :: PATCH /api/storage/volumes/b3e91ca2-12d5-11eb-a8ea-d039ea206f61/snapshots/196dbd30-bb4c-4c17-bde7-ba378edd36e6 : {"snaplock_expiry_time":"2024-10-07T23:15:59Z"} :: Success:
[kern_audit:info:3360] 8503ea00000d82ea :: NetAppRZ:ontapi :: <SVM_IP>:64314 :: <SVM_name>:vsadmin :: error-unknown-api :: Error: Unable to find API: cluster-identity-get