Hi,
thanks everybody for your help!!
I think with following your tips i will not run into any trouble!
Best Regards
Jochen
-----Original Message-----
From: Glenn Dekhayser [mailto:gdekhayser@voyantinc.com]
Sent: Wednesday, July 19, 2006 5:33 PM
To: Willeke, Jochen
Cc: toasters(a)mathworks.com
Subject: RE: Mapping of LUN's in Windows
Jochen:
After you've disabled the Exchange services, use SnapDrive to
'disconnect' (NOT delete) the LUN, move the filer and/or the hosts, then
use SnapDrive to 'connect' the existing LUN again to the old drive names
or mount points. If you've got multi-pathing, and you're using the
latest SnapDrive, you'll be able to choose the primary/preferred path to
the LUN.
This technique is supported, and will guarantee that your data within
the LUN remains consistent.
Glenn (the other one)
-----Original Message-----
From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Willeke, Jochen
Sent: Wednesday, July 19, 2006 4:15 AM
To: NetApp Toasters List
Subject: Mapping of LUN's in Windows
Hi toasters,
we want to move two Filers from one building to another. Due to this we
need to have a SAN redesign, as those filers host our exchange data.
In our HBA configuration we have currently automapping. So possibly it
could be that we have a WWPN with another SCSI ID after the change.
As we use snapdrive i suppose snapdrive to be responsible for the
coordination of LUN's to driveletters. But i am not really sure, so i
just want to ask some experts, if we can run into problems with wrong
driveletters after the change.
Has anybody experience with this?
Best Regards and thanks in advance
Jochen