Subscribe
Accepted Solution

Volumes left behind after verification completes

We have two MS Exchange 2003 clusters, V01 & V02. Each cluster has two nodes and runs Windows 2003. Ent. Ed, with SnapDrive 4.2.1 and SME 3.2. Looking to upgrade soon but not this week...

We use a 2nd server to verify the backups as the server load is high on the Exchange boxes.

The problem is once the verification has finished the flexclone volumes are sometimes left behind. It is normally just the transaction log volume or the database volume. The problem tends to happen on V01 more frequently and we have completed a bare metal re-install of the cluster nodes to try and resolve the issue. – No success.

There are no events on the Filer logs (FAS3070 cluster) and I have not been able to work out a pattern as to when it happens. The work around is to check the filer each morning for the flexclone volumes and offline / delete them.

Does anyone have any ideas to a possible solution. I have heard ESEUTIL throttling can cause this issue but testing has show the problem happens regardless.

Thanks for taking the time to read this and think about the issue. Any help / ideas welcome.

Re: Volumes left behind after verification completes

Hi Brendon...

I'm not sure why SME isn't cleaning up these volumes after the verification is complete. It should delete the works and leave everything clean.

Is there any info in the backup reports for a particular verification job that gives any clue as to what's happening? Or even the event logs on the verification server...those would be helpful to look at as well.

I'll follow up with a few folks to see if this is a known issue or not. I'll post what I find probably next week.

Thanks...

Shannon

Re: Volumes left behind after verification completes

Luck would have it that the issue happened over the weekend.

SnapDrive_gbdc01exmbf01db_clone_of_exchsnap__gbdc01exmbv01_09212008_190000__weekly_snapshot_0

The SME log is standard expect for this:

Operation completed successfully in 45.735 seconds.

Dismounting LUN C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint\MPDisk001 of Snapshot ...

The virtual disk may not be connected, because its mount point cannot be found.

(SnapDrive Error Code: 0xc0040221)

Re-trying to force dismounting LUN...

SnapManager will pause 70 seconds after force dismount, please wait...

SnapDrive failed to dismount the snapshot.

Error Code: 0xc0040221

The virtual disk may not be connected, because its mount point cannot be found.

Mounting Snapshot for LUN E of Computer GBDC01EXMBN02

Mount point directory

Snapshot will be mounted on subdirectory

This Snapshot is mounted as the drive .

Mount Snapshot succeeded.

RUNNING TRANSACTION LOG INTEGRITY VERIFICATION

Transaction log directory is located at:

C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint\MPDisk001\EXCHSRVR\MDBDATA\SG1\

Start running ESEUTIL on "C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint\MPDisk001\EXCHSRVR\MDBDATA\SG1\"...

Command: ["C:\Program Files\Exchsrvr\bin\eseutil.exe" /ml E00]

Checking...

Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...

************

Nothing on the Windows server log

*************

Console Messages

Sun Sep 21 20:04:54 BST : LUN /vol/SnapDrive_gbdc01exmbf01db_clone_of_exchsnap__gbdc01exmbv01_09212008_190000__weekly_snapshot_0/sg1db.lun unmapped from initiator group viaRP...

Sun Sep 21 20:05:04 BST : LUN /vol/SnapDrive_gbdc01exmbf01db_clone_of_exchsnap__gbdc01exmbv01_09212008_190000__weekly_snapshot_0/sg1db.lun has been taken offline

Sun Sep 21 20:05:08 BST : Volume 'SnapDrive_gbdc01exmbf01db_clone_of_exchsnap__gbdc01exmbv01_09212008_190000__weekly_snapshot_0' has been set temporarily offline

Re: Volumes left behind after verification completes

Think I have found the solution.

I was getting alot of Plug & Play errors in the System Log Event, Event ID 257, see Microsoft Article with Hotfix:

http://support.microsoft.com/kb/924390

Will try this weekend and report back.

Re: Volumes left behind after verification completes

Did you ever find a resolution for this? It looks to be a bug because there are many people running into the sdame issue.

Re: Volumes left behind after verification completes

Long story short, no. Hotfix was not the solution and filer CPU @ 100% was not the cause. Still looking for the answer.

Bren

Re: Volumes left behind after verification completes

Hey Ian/Brendon...

Was there a case opened with NGS for this issue? I'm going to bring this up with the engineers and see what we can figure out. But a case number would be good for them to get more info on what's happening.

Thanks...

Shannon

Re: Volumes left behind after verification completes

I have 3 different case numbers from the last 12 months. Out of the office this week but should be able to dig them out next week.

Re: Volumes left behind after verification completes

Is there any resolution on this yet? Also, I was wondering if it was a 64bit issue. We are experiencing the same issue and it's quite frustrating.

Thanks,

Carl.

Re: Volumes left behind after verification completes

64bit shouldn't have anything to do with volumes on the storage being left behind.

As soon as I get a case number that I can reference, I can do more investigating and see what I can figure out.

Thanks...

Shannon