H Nelson,
yes, we have the same problem at one customer side.
The environment is:
FAS 3240A
Ontap 8.1.2 7-mode
Snapdrive 6.4.2
SnapManager SQL 5.2
VSC 4.1
NFS based VMDKs
Same first Snapdrive errror on dismounting than yours, but secondary error code different:
[01:13:22.818] Database was detached successfully.
[01:13:22.824] Dismounting LUN C:\mnt\verify\MPDisk001 of SnapShot [sqlsnap__muc1s0043_12-12-2012_00.02.29__daily]...
[01:13:47.341] SnapDrive operation to dismount LUN in snapshot copy failed. SnapDrive error code: 0xc0041071
[01:14:00.923] SnapDrive operation to dismount LUN in snapshot copy failed. SnapDrive error code: 0x80010105
[01:14:00.927] Re-trying to force dismounting LUN...
[01:14:01.128] SnapDrive operation to force dismount LUN in snapshot copy failed. SnapDrive error code: 0xc0040221
[01:14:01.140] [SnapDrive Error]: The LUN may not be connected, because its mount point cannot be found. (SnapDrive Error Code: 0xc0040221)
[01:14:01.140] Dismounting LUN C:\mnt\verify\MPDisk002 of SnapShot [sqlsnap__muc1s0043_12-12-2012_00.02.29__daily]...
[01:14:10.416] SnapDrive operation to dismount LUN in snapshot copy failed. SnapDrive error code: 0xc0041071
[01:14:21.637] SnapDrive operation to dismount LUN in snapshot copy failed. SnapDrive error code: 0x80010105
[01:14:21.638] Re-trying to force dismounting LUN...
[01:14:21.810] SnapDrive operation to force dismount LUN in snapshot copy failed. SnapDrive error code: 0xc0040221
[01:14:21.810] [SnapDrive Error]: The LUN may not be connected, because its mount point cannot be found. (SnapDrive Error Code: 0xc0040221)
Same try to force dismount.
The error is shown on every dismount in the log, but the first dismounts are in reality succesfull. That´s why the force dismount failed, because than it´s already disconnected.
But after 7 succesfull dismounts (all 7 show the snapdrive error in log) the 8 one really miss.
It looks like a timeing problem !
History:
Last week we had Snapdrive 6.3P2 and Ontap 8.1.1 and every thing is running fine.
After an NFS outage during 2 VSC virtual machine restores, we decide to upgraded to Ontap 8.1.2 on last friday.
After that update SnapManager SQL can do succesful backups but cannot do verify´s because of the Snapdrive dismount errors.
There is no 6.4.2D1 or 6.4.2P1 at the moment, but this error smells like different function giveback codes on 8.1.2
The force dismount of snapdrive logs immediatly the errors (after 1 sek.)
Have you opened a case ?
Have you also Ontap 8.1.2 running ?
Is there feedback from NetApp ?
On our Exchange VM with iSCSI connected Raw Devices the old Snapdrive 6.3P2 works fine on that 8.1.2 based NetApp.
So i think it´s a problem with vmdk based SnapManager/Snapdrive installations and Ontap 8.1.2
Greetings
Roland
Nachricht wurde geändert durch: Roland Kurz