Skip to main content
NetApp Knowledge Base

Resolution Guide for the Mount-SdSnapshot failed issue in SMBR

  1. Last updated
  2. Save as PDF
Views:
503
Visibility:
Public
Votes:
0
Category:
single-mailbox-recovery-smbr
Specialty:
snapx
Last Updated:

Applies to

  • Single Mailbox Recovery (SMBR)
  • SnapCenter Server (SC)

Description

How to resolve common issues caused by the SMBR error Mount-SdSnapshot failed

Cause
Solution
Misconfigured or no iSCSI/FC connection between the SMBR server and the SVM Establish an iSCSI/FC connection
SC FQDN URL is not set in the SMBR server host registry Add a new string value called SMS Target URL to the SMBR host registry
Port 443 not open bidirectionally on SC and/or SMBR server hosts Open port 443 on the relevant host(s)
The aggregate where the volume/snapshot is stored is not in the aggregate list of the Storage Virtual Machine (SVM) Assign the aggregate to the correct SVM
Failing to mount snapshot from RDM disk Replace the SnapshotManager.exe, contact NetApp Technical Support
Exchange server with SnapCenter Plug-in for Microsoft Exchange Server (SCE)
is missing correct SnapDrive (SDW) Powershell Module		 Uninstall SCE/SDW and install SCE and SnapCenter Plug-in for Microsoft Windows Server (SCW) on the Exchange server host

 

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.