Backup Verification Error with SME 6.0 against an Exchange 2010

[mrphoenix]

Hi folks,

After some initial problems with installing SME 6.0 I finally got this solved. It was a permission problem on our DCs that drove our Exchange nuts ...

Finally I got the backup configured and running, now I'm having some other erros and don't know how so solve them. Maybe somebody can help?

I'm seeing these errors for each DB that has to be verified:

----------

EventSource: SnapDrive

EventID: 1116

Failed to connect to LUN. VDS volume object for the LUN s/n 'C4iAWJV2-xA3' has not been found
.

LUN Name = mec-eu02
Storage Path = /vol/vol2imx/.snapshot/exchsnap__framsexm10_02-21-2010_22.00.15/mx_db02/
Protocol Type = LUN
Storage System Name = franapfs0001
Requested Mount Point = franapfs0001:/vol/vol2imx/.snapshot/exchsnap__framsexm10_02-21-2010_22.00.15/mx_db02/mec-eu02
Assigned Mount Point = C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint\MPDisk001\

Error code :

----------

EventSource: SnapDrive

EventID: 178

Failed to connect the LUN in Snapshot copy (exchsnap__framsexm10_02-21-2010_22.00.15) as drive C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint\MPDisk001\ on the computer (FRAMSEXM10).

LUN Name = mec-eu02
Storage Path = /vol/vol2imx/mx_db02/
Protocol Type = LUN
Storage System Name = franapfs0001

Error code : VDS volume object for the LUN s/n 'C4iAWJV2-xA3' has not been found

----------

EventSource: SnapManager For Exchange

EventID: 245

SnapManager database integrity verification did not complete after the backup on server 'FRAMSEXM10' for storage group/database 'mec-eu02'.

---------

EventSource: SnapManaer For Exchange

EventID: 246

SnapManager database integrity verification did not complete after the backup on server 'FRAMSEXM10' for storage group/database 'mec-eu02'.

---------

EventSource: SnapManager for Exchange

EventID: 274

Exchange writer will not truncate transaction log files because SnapManager backup verification for 'mec-eu02' failed. The SnapManager backup verification failure should be resolved right away as transaction log LUN can run out of disk space.

Component name: 99453e30-3913-4bf0-8b55-a3b136713678

---------

EventSource: MSExchangeIS

EventID: 9782

Exchange VSS Writer (instance 052d09e3-50b3-4ef9-99d8-e4621882d62b:8) has completed the backup of database 'mec-eu02' with errors. The backup did not complete successfully, and no log files were truncated for this database.

---------

EventSource: ESE

EventID: 2007

Information Store (3608) Shadow copy instance 8 aborted.

For more information, click http://www.microsoft.com/contentredirect.asp.

Hopefully somebody knows what to do!

Best regards,

Philipp

[lwei]

I sometimes reboot the server and that resolves the "RPC-Server not available"issue. Just a thought.   -Wei

[mrphoenix]

Hi wei,

I've rebooted about 1000 times by now - no change

Greetings,

Philipp

[mrphoenix]

Good Morning,

DNS is working fine and there are no related error-messages.

The Guys from the firewall-team don't see any drops, either...

Greetings,

Philipp

[thomas_glodde]

mrphoenix,

you are running in the same bug as me, have a look at this:

https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb56220

There are several configuration issues that can lead to this error appearing and preventing operations such as a snapshot mount from within SnapDrive.  Verifying the following Windows hotfixes and system defaults below often resolve the snapshot mounting issues encountered on Windows servers through SnapDrive:

I) Install http://support.microsoft.com/kb/975921

II) Verify the "SAN Policy" setting in Windows DISKPART is set to the default value of "Offline Shared"

1. Open a Windows Command Prompt (CLI)
2. Type "diskpart" at the prompt, and hit <enter>
3. At the DISKPART> prompt, type "san":
        DISKPART> san
        SAN Policy  : Online All
4. If the current setting is not the Windows default of "offline shared"; Type "san policy=offlineshared":
        DISKPART> san policy=offlineshared
        DiskPart successfully changed the SAN policy for the current operating system.
5. Type "san" to verify it has been changed to "Offline Shared":
        DISKPART> san
        SAN Policy  : Offline Shared

III) If you are still unable to mount a snapshot using SnapDrive, try completing the following steps:

1. Open a Windows Command Prompt (CLI)
2. Type "diskpart" at the prompt, and hit <enter>
3. At the DISKPART> prompt, type "automount disable"

After completing these changes, SnapDrive should be able to successfully mount a snapshot of a LUN on the same Windows Server 2008 system when the original LUN is mounted.

Kind regards,

Thomas

[mrphoenix]

Hi Thomas,

The Hotfix in Conjunction with the options set in diskpart did the trick!

Thanks for this great advice. I'm now able to mount the snapshot - I think the backup should work tonight as it is intended 🙂

Now I can play around with recovering the backed up data soon.

Many thanks,

Philipp

[yaohui]

Hi Thomas,

IHAC who entering the same problem while using Win 2008 R2.

I skipped installation of the hotfix you mentioned and went straight for step 2, and it works fine now 😃

Thanks for your recommendations!

Yaohui

[thomas_glodde]

Hi folks,

be sure to check SnapDrive v6.2P1:

http://now.netapp.com/NOW/download/software/snapdrive_win/6.2P1/

Date Posted: 12-MAR-2010

SnapDrive 6.2P1
Based on SnapDrive 6.2
03/10/2009

Bugs fixed in this release:


6.2P1
===========
 397424 |SDW: Lun restore fails IOCTL_DISK_SET_DRIVE_LAYOUT_EX on reversed snapmirror destination
 
 382378 |stale entries in reg HKLM\SYSTEM\CurrentControlSet\Services\ontapdsm\Parameters\LUNS\<filer>\<serial#>

 390915 |SDW Service is dependent on the availability of VMware vCenter Server

 393518 |SnapDrive 6.2 fails to create RDM LUNs with ESX iSCSI when FCP license is not set on the filer

 393770 |SnapDrive sending an ASUP msg "This volume is not designated for thin provisioning".

 395057 |SMHV does not work on Japanese Windows OS

 397462 |Windows 2008R2 120s Volume Arrival Timeout when connecting to LUN Clone on the same host

 397866 |Snapshot mounts are very slow

 398316 |upgrade to main from sdw 6.2 gets runtime error. program: navssprv.exe

Its fixed now 😉

Kind regards

Thomas

[udom_sukij]

Dear all,

I also have the same problem to mount database of MS exchange but for the log drive is work smootly.

Regards,

Sukij

[lwei]

Hi Sukij,

Is your mount problem resolved? If not, you can try the steps Thomas posted in this thread.

Regards,

Wei

[udom_sukij]

Dear Sir,

Right now I can mount with Snapdrive GUI from the command in attached mail. And I upgrade Snap from 6.1 to 6.2 I have problem with SDCLI command line . I'm not sure it possible or not as MS Exchange server 2007 have Snapdrive 6.1 and Backup server have Snapdrive 6.2.

When I used command to mount Snapshot from MS Exchange Server still have another error (Access denied) in attached, I also change the DCOM permission is not solved the problem.

HOST : W2008R2 Snapdrive 6.2

Guest : W2008 Standard Snapdrive 6.1

Backup Server: W2008R2 Snapdrive 6.1

I also try to uninstall Snapdrive 6.2 and install Snapdrive 6.1 (error ) pls. let me know how to fix

Regards,

Sukij

[udom_sukij]

Hi Lwei,

I already install Snapdrive 6.2P1 on the backup server but is still the same when I used the SDCLI in below

error from Command Prompt

"C:\Program Files\NetApp>sdcli snap mount -r thbkkexc137 -k M -s eloginfo__thbkke
xc137__04-07-2010_20.00.00.29__daily -d c:\exchange\log3
Initializing...Unable to connect to the LUN in Snapshot.
Error: Access is denied.

error from event log (application)

Log Name:      Application
Source:        SnapDrive
Date:          4/16/2010 4:15:18 PM
Event ID:      178
Task Category: Generic event
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      THBKKSRV150.canadoil.int
Description:
Failed to connect the LUN in Snapshot copy (eloginfo__thbkkexc137__04-07-2010_20.00.00.29__daily) as drive  on the computer (THBKKSRV150).

LUN Name = Not available
Storage Path = Not available
Protocol Type = LUN
Storage System Name =

Error code : Access is denied.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SnapDrive" />
    <EventID Qualifiers="0">178</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-04-16T09:15:18.000000000Z" />
    <EventRecordID>162361</EventRecordID>
    <Channel>Application</Channel>
    <Computer>THBKKSRV150.canadoil.int</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Not available</Data>
    <Data>Not available</Data>
    <Data>LUN</Data>
    <Data>
    </Data>
    <Data>Access is denied.
</Data>
    <Data>eloginfo__thbkkexc137__04-07-2010_20.00.00.29__daily</Data>
    <Data>
    </Data>
    <Data>THBKKSRV150</Data>
  </EventData>
</Event>

Please see the attached file that I can run SDCLI disk list

I don't why in Snapdrive GUI can connect.

Does anyone know please !!!.

Regards,

Udom_sukij

[lwei]

Look like your sdcli syntax was not correct. Could you see what exactly was done when you used the GUI? Make sure you use the same parameters when using sdcli. I think you need to at least specify -k and -m (may be case sensitive).

Thanks,

Wei

[udom_sukij]

Dear  Lwei and Thomas,

Thank you for your support, It work every think that fixed my issued.

Regards,

Sukij

[lwei]

Hi Sukij,

You're very welcome. Glad to know it worked!

Regards,

Wei

[udom_sukij]

Dear Lwei,

The Snapdrive, If we need to mount from SDCLI we need the same version

right ? If I used -r on the backup server is still problem

Regards,

Sukij