Skip to main content
NetApp Knowledge Base

Exchange backup fails due to lack of space on the storage volumes

Views:
60
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for Microsoft Exchange Server (SCE)

Issue

  • SCE backup fails with the error seen in the <installation_path>\Program Files\NetApp\SnapCenter\SMCore\log\SMCore_<id>.log when SCE is trying to rename the VSS snapshot:

Activity 'Renaming VSS Snapshot' failed with error: Rename snapshot '{bdf2517d-67de-430b-8f72-5552835bf94b}' failed: entry doesn't exist .Failed in volume '<vol_name>', entry doesn't exist Failed in volume '<vol_name>', entry doesn't exist Failed in volume '<vol_name>', entry doesn't exist Failed in volume '<vol_name>', entry doesn't exist Failed in volume '<vol_name>', entry doesn't exist Failed in volume '<vol_name>', entry doesn't exist

  • Storage confirms the error:

RenameSnapshot Request:  -Volume <vol_names>, -Snapshot {VSS_snapshot} -NewName <snapshot_name> -StorageSystem <SVM_name>
DEBUG SMCore_1881780 PID=[34132] TID=[137] Command: Rename-NcSnapshot. Storage System: <SVM_IP>. Version: NetApp Release 9.15.1P6: Wed Dec 04 01:42:39 UTC 2024. Connection Mode: ZAPI. Username: vsadmin.

 

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.