Hi all, this is a little bit OffTopic, but hurts us at least twice a month ... We have some "Dedicated Storage Nodes", which share fibre attached LTO drives in an 3-frame IBM3584. Switches\Directors
Author: Davina Treiber <DavinaTreiber AT PEEVRO.CO DOT UK>
Date: Wed, 6 Sep 2006 11:55:38 +0100
Hi all, this is a little bit OffTopic, but hurts us at least twice a month ... We have some "Dedicated Storage Nodes", which share fibre attached LTO drives in an 3-frame IBM3584. Switches\Directors
Author: "Greggs, Dana" <c-dgreggs AT STATE.PA DOT US>
Date: Wed, 6 Sep 2006 09:01:04 -0400
You can do it in Windows but the flag is not set "in Windows" but on the device. I have 4 FC attached libraries on W2K3 and it works. There is a caveat in that at times I have to resync the Library a
Author: "Greggs, Dana" <c-dgreggs AT STATE.PA DOT US>
Date: Wed, 6 Sep 2006 08:57:57 -0400
You have to enable persistent binding. The method varies according to the hardware manufacture but you must do it on the HBA and the FC bridge of the tape library. Thanks, Dana --Original Message-- F
Behavior like this is what forced us to disable and uninstall all our Windows dedicated storage nodes. -Teresa Hi all, this is a little bit OffTopic, but hurts us at least twice a month ... We have s
Author: Davina Treiber <DavinaTreiber AT PEEVRO.CO DOT UK>
Date: Wed, 6 Sep 2006 15:05:53 +0100
You have to enable persistent binding. The method varies according to the hardware manufacture but you must do it on the HBA and the FC bridge of the tape library. Persistent binding is not sufficie
YES, Davina matches exactly the point (which she does most of the time :-) [ enjoy your postings very much -sg-] Persistent binding would only help, if NetWorker could work with physical addresses li
Author: Davina Treiber <DavinaTreiber AT PEEVRO.CO DOT UK>
Date: Wed, 6 Sep 2006 16:54:52 +0100
Persistent binding is not sufficient to totally solve this problem. Persistent binding locks down the binding of WWPN or WWNN to SCSI b.t.l addresses. It does not control the mapping of SCSI address
Author: "Greggs, Dana" <c-dgreggs AT STATE.PA DOT US>
Date: Wed, 6 Sep 2006 12:39:51 -0400
That's why I said you also have to configure the FC Bridge/Router on the Library and enable "device mapping" which in essence maps a SCSI ID to a FC LUN. I use IBM 4560LX's (aka Neo2000's) and config
Author: Brian Narkinsky <BNarkinsky AT CCLAFLORIDA DOT ORG>
Date: Wed, 6 Sep 2006 15:40:28 -0400
I was never able to get totally rid of the problem. But I was able to get it down to where it only bit us every 3 or 4 months. And then if I got the reboot order just right it usually did not happen.
Author: Brian Narkinsky <BNarkinsky AT CCLAFLORIDA DOT ORG>
Date: Wed, 6 Sep 2006 15:52:31 -0400
You can reboot the FC-SCSI bridges and sometimes that helps. But sometimes the problems occurs when that happens. This was on HP hardware and YMMV. I know the drive serialization was supposed to work
No Fibre-to-SCSI-Bridges here, only plain FibreChannel. ( And no HSG80 controllers or even HSV210s :-) That would give some new hope, perhaps. We have scheduled to start with 7.3.1 or 7.3.2 in Novem
Don't have your hopes up too high, In our installation 7.3.1 on W2003 with San attached Storagetek SL500 + 2 LTO-3 The serial numbers were not recognized (complaints about them being too long) and yo
Sorry, I don't have anything to offer on the Windows/SAN front. But I know when we transitioned from Solaris to Linux, which (at least by default) remaps on each reboot, I was annoyed that /dev/nstX