2014-11-14 08:48 AM
Let me start by saying that this is my first experience with NetApp. Someone else setup the Exchange 2010 backups and I've been asked to troubleshoot this verification failure.
We are using Data ONTAP 8.1.2P3 7 and SnapManager for Exchange 6.0.2, to backup our single Exchange 2010 SP3. The backup job's verification server is the Exchange server and the VDS service is started.
I believe this started only recently, that we receive e-mails similar to the following e-mail:
Message: HA Group Notification from filer1 (CLIENT APP ERROR General: SME Version 6.0.2: (131) on server1: Verification of the Exchange databases failed. (Exchange 18.104.22.168) Verification failed. Error code: 0xc00402ba, LUN: I:\) WARNING
Log Example: GENERATED_ON=Sun Nov 09 02:03:51 MST 2014
VERSION=Data ONTAP Release 8.1.2P3 7-Mode: Wed Feb 20 19:56:15 PST 2013
We also see the following events in the Application log on the Exchange server:
Error 11/14/2014 2:03:06 AM SnapDrive 178 Generic event
Log Name: Application
Date: 11/14/2014 2:03:06 AM
Event ID: 178
Task Category: Generic event
Failed to connect the LUN in Snapshot copy (exchsnap__server1_11-14-2014_02.02.40) as drive C:\Program Files\IBM\SnapManager for Exchange\SnapMgrMountPoint\MPDisk598\ on the computer (SERVER1).
LUN Name = iSCSI_Server1_DB2
Storage Path = /vol/iSCSI_Server1_DB2_vol/
Protocol Type = HTTPS
Storage System Name = filer1
Error code : The target LUN in Snapshot copy is inconsistent or does not exist and cannot be connected.
<Provider Name="SnapDrive" />
<TimeCreated SystemTime="2014-11-14T09:03:06.000000000Z" />
<Data>The target LUN in Snapshot copy is inconsistent or does not exist and cannot be connected.
<Data>C:\Program Files\IBM\SnapManager for Exchange\SnapMgrMountPoint\MPDisk598\</Data>
I have also verified that all of the VSS writers are stable and have attached the most recent backup log. It looks to me, like the snapshot is being created just fine, so I don't know why it cannot be connected. I searched the KB for "0xc00402ba", but only got one related article (1010785, which discusses backup failures).
Finally, I saw this NetApp thread, in which it is suggested a Microsoft hotfix and a change to the server's SAN policy (by THOMAS_GLODDE) would resolve the issue. I'm willing to give those steps a try, but am skeptical, because only one of my three databases, is not being verified.
Any thoughts on how to troubleshoot this? Thanks.
Solved! SEE THE SOLUTION
2014-11-19 09:46 PM
There is a public report for this http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=556102