Subscribe

SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Hi folks,

upon mounting a snapshot LUN using SnapDrive 6.2 on Windows Server 2008 R2, the operation times out after 120. If i check disk management during disk mount, i see the lun clone as "offline", telling me "die disk is offline because it has a signature collision woth another disk that is online".

Configuration fits the IMT perfectly.

Any suggestions?

Thanks & kind regards

Thomas

Re: SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Hi Thomas,

What are the steps to reproduce the problem? If it is reproducible, then maybe you should report a bug.

Just my 2 cents,

Wei

Re: SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Hi Wei|

I use Windows 2008 R2 englisch RTM on vSphere 4. Regardless of iSCSI in the VM or iSCSI/FC RDM, create and connect works but connecting a snapshot LUN (eg Exchange

2010 Verify) fails with the error mentioned above¤

I cannot seem to be the only one having & testing such a configuration can i?!

Kind regards,

Thomas

Re: SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Not sure if this applies or not, but may be worth a try.  https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb56220

On the Windows host

Open a command prompt, and type “diskpart”

DISKPART> san

SAN Policy  : Online All

DISKPART> san policy=offlineshared

DiskPart successfully changed the SAN policy for the current operating system.

DISKPART> san

SAN Policy  : Offline Shared

Re: SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Daniel,

Good idea, will give it a try! Have just been playing around with mountvol.

Thanks

Thomas

Re: SnapDrive 6.2 on Windows Server 2008 R2 disk signature collision

Works like a charm! Thanks alot!