Skip to main content
NetApp Knowledge Base

SCE database restore fails

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

Applies to

SnapCenter Plug-In for Exchange 4.6 (SCE)

Issue

During SCE restore, when querying cloned LUN metadata, SCE and Ontap AuditMlog show respectively below errors:

2022-06-07T13:37:48.0813960+02:00 Error SCE PID=[2600] TID=[11000] Mount database failed with error 'Error. Failed to mount the Snapshot copy.Failed to mount the resource: D:\Program Files\Microsoft\Exchange Server\V15\Mailbox\MB1\ from snapshot: JRG1_Dom1_lab_server1_06-07-2022_04.04.09.0309. Failed to set the LUN signature.
entry doesn't exist

2022-06-15 11:01:15,325 [Pipeline Execution Thread] DEBUG NetApp.Ontapi.NaServer - <netapp version='1.7' xmlns='http://www.netapp.com/filer/admin' vfiler='ncv00266ps'><lun-get-geometry>
<path>/vol/srp18436wn_zrhmdb223SiClone9061d4c0_3ce2_4cc7_967a_a115d1e2e280/zrhmdb223</path>
</lun-get-geometry></netapp>
2022-06-15 11:01:15,368 [Pipeline Execution Thread] DEBUG NetApp.Ontapi.NaServer - <results reason="entry doesn't exist" status="failed" errno="15661"/>
2022-06-15 11:01:15,370 [Pipeline Execution Thread] ERROR DataONTAP.C.PowerShell.SDK.NcControllerCmdlet - API exception
NetApp.Ontapi.ErrnoException+EOBJECTNOTFOUND: entry doesn't exist
 

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.