SME 5 is not clearing down snapmirror verification volumes

[BrendonHiggins]

I do not have any error messages but SME5 is leaving behind the transaction log flexclones on the verification server once the job has finished.

I have to go in and manually remove them.

Any ideas?

Brendon

[BrendonHiggins]

Also the mount point folder is left behind.  I have just tried adding the preferred filer for both the source and snapmirror destination filers.

[swhitehead]

Howdy-

Anything ever come of this?  I've got a similar issue where LUNs are not detaching from the verify server.  As a result they're getting snapshotted and then can't be deleted without deleting a bunch of backups in the process.  I'm going to try the usual array of version updates to see where that gets me.

Thanks,
Scott

[BrendonHiggins]

The problem is intermitant and it has been a long time since it has last happened.  We have added new Exchange clusters, so there are less mailboxes per server, so this may of helped.

Sorry I do not know how the issue was resolved.

Bren

[radek_kubka]

Hi Bren,

Did you manage to find any solution for this yet?

If not - is there any interesting info in SME logs? (I mean SnapManager logs, not Exchange logs )

Regards,

Radek

[radek_kubka]

Also - is there anything suspicious in SnapDrive logs?

[swhitehead]

Hmmm.  Logs.  Great idea.

Found this -

"removal of the specified virtual disk was vetoed"

and then this -

http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=229810

which says this -

"Fixed in 5.0"
Which is sadly not the case.  We're on 5.0.1.

More logs below-

FCPVdisk.cpp@4276  Trying to remove disk object based on instance name '\\?\mpio#disk&ven_netapp&prod_lun&rev_0.2_#1&7f6ac24&0&36304139383030343836453246363136333334353535333332333835383736#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'
01/25-10:36:08.662 PID:2360 TID:1972 VDBase.cpp@623  Start DevSafeRemoveByName
01/25-10:38:16.675 PID:2360 TID:2372 DeviceEventsWindow.cpp@30  DBT_DEVNODES_CHANGED. A device has been added to or removed from the system.

01/25-10:38:16.722 PID:2360 TID:2372 DeviceEventsWindow.cpp@30  DBT_DEVNODES_CHANGED. A device has been added to or removed from the system.

01/25-10:38:16.738 PID:2360 TID:2372 DeviceEventsWindow.cpp@30  DBT_DEVNODES_CHANGED. A device has been added to or removed from the system.

01/25-10:38:16.738 PID:2360 TID:1972 VDBase.cpp@691  The removal of the specified virtual disk was vetoed. The disk could be in use. Try removing it later, or as a last resort, use the "Force Disconnect Disk" option.
HRESULT 0xc0040217.
01/25-10:38:16.753 PID:2360 TID:1972 VDBase.cpp@734  Finish DevSafeRemoveByName
01/25-10:38:16.800 PID:2360 TID:1972 MsftISCSIDriver.cpp@1412  CMsftISCSIDriver::bindPersistentLUNS Succeeded
01/25-10:38:16.800 PID:2360 TID:1972 ShootRebootDialog.cpp@512  Reset ShootReboot event
01/25-10:38:16.800 PID:2360 TID:1972 VirtualDiskProgress.h@21  Start CVirtualDiskProgress::~CVirtualDiskProgress

01/25-10:38:16.800 PID:2360 TID:1972 VirtualDiskProgress.h@25  Finish CVirtualDiskProgress::~CVirtualDiskProgress

01/25-10:38:16.800 PID:2360 TID:1972 Sychronize.h@108  Mutex::Release called

01/25-10:38:16.800 PID:2360 TID:1972 Sychronize.h@118  Mutex::Release finished execution

01/25-10:38:16.800 PID:2360 TID:1972 filer.cpp@889  Trying to get filer version for '10.250.160.70'
01/25-10:38:16.800 PID:2360 TID:1972 filer.cpp@902  The 'system-get-version' ZAPI is being called.

01/25-10:38:16.863 PID:2360 TID:1972 filer.cpp@914  Filer '10.250.160.70' runs 'NetApp Release 7.2.6.1: Wed Dec 10 21:10:08 PST 2008' version
01/25-10:38:16.863 PID:2360 TID:1972 filer.cpp@5141  The 'lun-get-attribute' ZAPI is being called.

01/25-10:38:16.878 PID:2360 TID:1972 filer.cpp@3978  The 'lun-list-info' ZAPI is being called.

01/25-10:38:16.878 PID:2360 TID:1972 VirtualDiskShare.cpp@1913  The virtual disk type is not recognized, or supported.
HRESULT 0xc004023c.

[swhitehead]

NetApp Tech Support helped us out with this one.  Bottom line was uninstalling the virus software on the Verify server made the problem go away.  So we tweaked the config of virus scanning and the problem is now much less of an issue.

Scott