topic SMVI errors Could not find current snapshot name in ONTAP Discussions

SMVI errors Could not find current snapshot name

chris_liberty — Thu, 05 Jun 2025 06:46:28 GMT

We receive these errors every time SMVI trys to run a backup. It is looking for really old snapshots that no longer exist. My question is, where does SMVI store this data? Is there a file some where that records the time based snapshot data that needs to be reset?

2011-09-08 11:36:29,038 ERROR - Could not find current snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 or original snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 for volume 0055-iccu-den01:/vol/ICCU_Windows_AppData_T4_NAS_PDEN01

2011-09-08 11:36:29,147 ERROR - Could not find current snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 or original snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 for volume 0055-iccu-den01:/vol/ICCU_Linux_AppData_T4_NAS_PDEN01

2011-09-08 11:36:29,272 ERROR - Could not find current snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 or original snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 for volume 0055-iccu-den01:/vol/ICCU_Linux_OS_T4_NAS_PDEN01

2011-09-08 11:36:29,381 ERROR - Could not find current snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 or original snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 for volume 0055-iccu-den01:/vol/ICCU_Linux_OS_T4_NAS_PDEN03

2011-09-08 11:36:29,506 ERROR - Could not find current snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 or original snapshot name smvi_Tier4_DEN_24Hours_novmsnap_20110403230000 for volume 0055-iccu-den01:/vol/ICCU_Linux_AppData_T4_NAS_PDEN03

2011-09-08 11:36:29,709 ERROR - Snapshot 'smvi_Tier4_DEN_24Hours_novmsnap_20110403230000' was not deleted as other applications 'snapvault' were dependent on it.

2011-09-08 11:36:29,709 WARN - Unable to delete backup in BackupRetention because of Snapshot 'smvi_Tier4_DEN_24Hours_novmsnap_20110403230000' was not deleted as other applications 'snapvault' were dependent on it.

I can't find any info on where this old snapshot might be stored.

Any help would be great,

Thanks,

Chris

SMVI errors Could not find current snapshot name

wes_beckum — Thu, 22 Sep 2011 19:21:14 GMT

Chris,

It looks like you have a Snapvault relationship established with this volume as well. If you do a "snap list volname" or through FilerView manage the volume's Snapshots, you will probably see that the above referenced Snapshot's status is "snapvault". That means it was used as the baseline for the Snapvault relationship and is now locked.

Looking at your Snapshot naming convention, it appears you are using the default naming scheme. There is an option where rather than "smvi_Tier4_DEN_24Hours_novmsnap_20110403230000", the Snapshot would be named "smvi_Tier4_DEN_24Hours_novmsnap_recent". You can then update your Snapvault relationship using a Snapshot name that will be static and the Snapmanager product will be able to rename and delete Snaps based on retention settings.

Wes

SMVI errors Could not find current snapshot name

chris_liberty — Mon, 03 Oct 2011 16:06:05 GMT

Thanks for the reply. These are what my snap lists look like on the primary and secondary. I see no traces of the snap shot these errors are talking about. Is there any way to reset this snap so it stops trying to search for it?

Secondary filer

Volume ICCU_Linux_AppData_T4_NAS_SV_PDIN01
working...

%/used       %/total date          name
---------- ---------- ------------ --------
0% ( 0%)    0% ( 0%) Oct 03 02:02 ICCU_Linux_AppData_T4_NAS_PDIN01.0
0% ( 0%)    0% ( 0%) Oct 03 01:44 0055-nrstr-c2(0118072036)_ICCU_Linux_AppData_T4_NAS_SV_PDIN01-base.1 (busy,snapvault)
3% ( 3%)    1% ( 1%) Oct 02 09:56 ICCU_Linux_AppData_T4_NAS_PDIN01.1
9% ( 6%)    3% ( 2%) Oct 01 02:59 ICCU_Linux_AppData_T4_NAS_PDIN01.2
13% ( 4%)    5% ( 2%) Sep 30 14:59 ICCU_Linux_AppData_T4_NAS_PDIN01.3
16% ( 4%)    6% ( 2%) Sep 29 13:39 ICCU_Linux_AppData_T4_NAS_PDIN01.4
19% ( 3%)    7% ( 1%) Sep 29 05:42 ICCU_Linux_AppData_T4_NAS_PDIN01.5
26% (11%)   12% ( 4%) Sep 28 04:11 ICCU_Linux_AppData_T4_NAS_PDIN01.6
28% ( 3%)   13% ( 1%) Sep 27 11:57 ICCU_Linux_AppData_T4_NAS_PDIN01.7
30% ( 4%)   14% ( 1%) Sep 27 02:01 ICCU_Linux_AppData_T4_NAS_PDIN01.8
32% ( 5%)   15% ( 2%) Sep 26 12:17 ICCU_Linux_AppData_T4_NAS_PDIN01.9
35% ( 6%)   18% ( 2%) Sep 25 01:40 ICCU_Linux_AppData_T4_NAS_PDIN01.10
35% ( 0%)   18% ( 0%) Sep 24 11:13 ICCU_Linux_AppData_T4_NAS_PDIN01.11
38% ( 7%)   20% ( 2%) Sep 23 02:33 ICCU_Linux_AppData_T4_NAS_PDIN01.12
40% ( 5%)   22% ( 2%) Sep 22 02:36 ICCU_Linux_AppData_T4_NAS_PDIN01.13
41% ( 4%)   23% ( 1%) Sep 21 02:09 ICCU_Linux_AppData_T4_NAS_PDIN01.14
43% ( 5%)   25% ( 2%) Sep 20 17:18 ICCU_Linux_AppData_T4_NAS_PDIN01.15
44% ( 4%)   26% ( 1%) Sep 19 02:13 ICCU_Linux_AppData_T4_NAS_PDIN01.16
45% ( 3%)   27% ( 1%) Sep 18 06:08 ICCU_Linux_AppData_T4_NAS_PDIN01.17
46% ( 2%)   28% ( 1%) Sep 17 16:27 ICCU_Linux_AppData_T4_NAS_PDIN01.18
46% ( 2%)   28% ( 1%) Sep 17 12:37 ICCU_Linux_AppData_T4_NAS_PDIN01.19

Primary filer

[root@lx-hsstmon-p01p ~]# ssh root@0055-nas-cl10-c1 snap list ICCU_Linux_AppData_T4_NAS_PDIN01
Volume ICCU_Linux_AppData_T4_NAS_PDIN01
working...

%/used       %/total date          name
---------- ---------- ------------ --------
3% ( 3%)    0% ( 0%) Oct 02 23:28 smvi_Tier4_DIN_24Hours_novmsnap_recent (snapvault)
7% ( 4%)    0% ( 0%) Oct 01 23:28 smvi_Tier4_DIN_24Hours_novmsnap_20111001230000
12% ( 6%)    1% ( 0%) Sep 30 11:59 smvi_Tier4_DIN_24Hours_novmsnap_20110927230001

Re: SMVI errors Could not find current snapshot name

wes_beckum — Mon, 03 Oct 2011 20:00:37 GMT

Chris,

Did you just recently change the naming scheme to "xxxx_recent"?

One thing you could do, probably not best practice, but manually create a snapshot in that volume using "snap create" with the snapshot named the above referenced snap that SMVI is trying to delete. SMVI "should" delete that snap the next time the scheduled job kicks off.

Wes