Skip to main content
NetApp Knowledge Base

SCE SnapShot name is the UUID and the snaplock_expiration_time is not set

  1. Last updated
  2. Save as PDF
Views:
94
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter 5.0, 5.0p1 (SC)
SnapCenter Plug-in for Exchange (SCE)

Issue

Following an upgrade from SnapCenter (SC) 5.0 to 5.0P1, the SnapShots on an SCE host are displayed as UUIDs, and the snaplock_expiration_time is no longer set.

In the management audit log (mlog), the following error is repeatedly shown:

Netapp:http ::<IP:PORT> :: <SVM>:vsadmin :: POST/api/private/cli/volume/snapshot/rename :{"vserver":"<SVM>.cii_encrypt/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=/cii_encrypt","volume":"vol_anon_db01_logs","snapshot":"{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}","new-name":"anon_DB01_ANON_09-04-2024_19.40.35.2841"} :: Pending 


NetApp:http :: <IP:PORT>:: <SVM>:vsadmin :: POST/api/private/cli/volume/snapshot/rename :{"vserver":"<SVM>.cii_encrypt/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=/cii_encrypt","volume":"vol_anon_db01_logs","snapshot":"{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}","new-name":"anon_DB01_ANON_09-04-2024_19.40.35.2841"} :: Error: Specified Vserver not found

 
SMCore log displays the following error :
DEBUG SMCore_25634 PID=[23936] TID=[3] Command: Invoke-NcCli. Storage System: <SVM IP>. Version: NetApp Release 9.14.1P7: Thu Aug 01 03:07:44 UTC 2024. Connection Mode: REST
DEBUG SMCore_25634 PID=[23936] TID=[3] ex.Message : The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: [400]: Specified Vserver not found
 
Since the snapshot was not renamed, the attempt to set the SnapLock expiration time failed immediately:

2024-09-04T19:51:24.2602265+02:00DEBUG SMCore_25634 PID=[23936] TID=[3] SetSnapLockExpirationTimeActivityStarted

2024-09-04T19:51:24.2652388+02:00ERROR SMCore_25634 PID=[23936] TID=[3] Set SnapLock Expiration Time Failed forall SnapShots.

2024-09-04T19:51:24.2652388+02:00ERROR SMCore_25634 PID=[23936] TID=[3] Set SnapLock Expiration Time Failed,Reason: Object reference not set to an instance of an object.

2024-09-04T19:51:24.2652388+02:00DEBUG SMCore_25634 PID=[23936] TID=[3] SetSnapLockExpirationTimeActivity End

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.