Networker

Re: [Networker] Switching library from SCSI to FiberChannel - any caveats?

2004-11-24 13:16:45
Subject: Re: [Networker] Switching library from SCSI to FiberChannel - any caveats?
From: Teresa Biehler <tpbsys AT RIT DOT EDU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Wed, 24 Nov 2004 13:14:45 -0500
You'll need a license for DDS (dynamic drive sharing) if you want
multiple storage nodes to use the same tape drive.  Also, be sure to
review old messages from this list about bus resets.  Having things set
up incorrectly can result in data loss.

-Teresa

-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On Behalf Of Matt Cowger
Sent: Wednesday, November 24, 2004 12:53 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Switching library from SCSI to FiberChannel -
any caveats?

Honestly, I don't know.  We don't run Exchange, and don't use
storagenodes, so someone else will have to answer that.

Its was pretty easy for me, the only hangup being the changes to
modules.conf and rebuilding the initrd...I think its stupid that redhat
doesn't configure their kernels with 'probe all luns', but hey, thats
life.

Brian O'Neill wrote:
> Excellent. Pretty much as I expected.
>
> Supposedly, the Exchange servers will also talk to the jukebox
directly,
> as "storage" nodes (I think that's the correct terminology). Can
> multiple node share the same tape drive?
>
> Matt Cowger wrote:
>
>> Ha!  I just did this!
>>
>> We are running RHEL3 on a Dell with a Qlogic FCHBA -> Brocade 3250 ->
>> SpectraLogic 20K.
>>
>> My process was this:
>>
>> 1.  Use the gui to delete the jukebox.
>> 2.  Shutdown the server
>> 3.  Shutdown the library
>> 4.  Install the HBA
>> 5.  Install the QIP for the library
>> 6.  Connected them up to the switch, and zoned it out so only those 2
>> can see eachother.  This is important in case you have other machines
on
>> the SAN that might try to talk to your drives/changer.
>> 7.  Startup the library, then the server
>> 8.  The server should see at least the changer (check dmesg) if not
the
>> drives.  If the drives are not found, it may be that all the scsi
luns
>> are not being probed.  If they aren't, you'll need to mody your
>> initrg.gz to make it probe all the LUNs on a SCSI device (FC devices
>> appear as SCSI devices, and go through the scsi_mod layer.  To edit
your
>> initrd:
>>
>> in /etc/modules.conf, add:
>> options scsi_mod max_scsi_luns=128
>>
>> Then, rebuilt your initrd with:
>> mkinitrd -f /boot/initrd-<kernel>.img <kernel>
>> where <kernel> is the output from 'uname -r'.  Mine is
2.4.21-20.ELsmp
>>
>> 9.  Then reboot, and you should get the drives listed in dmesg as st
>> devices.
>> 10.  Use jbconfig to setup your jukebox again.
>> 11.  Run a nsrjb -HEvvv and nsrjb -Ivvvv
>> 12.  Sit back!
>>
>> Best,
>>
>> Matt
>>
>>
>> Brian O'Neill wrote:
>>
>>> A client of mine decided to purchase a FiberChannel-based solution
to
>>> backup their new Exchange servers to the existing Dell PowerVault,
>>> requiring that the backup server (running RedHat AS2.1) also be
>>> converted to FiberChannel - without even mentioning this fact to me
>>> until they said they needed to install the HBA...
>>>
>>> I'm a rookie when it comes to making FC stuff work. The HBA is in
place
>>> and the OS sees it fine. Now I have to have them reconnect the PV
via
>>> fiber.
>>>
>>> I'm running Networker 7.1.1. What difficulties may I come across?
Should
>>> I delete the drive and library first, rediscover them, then
re-inventory
>>> the library? Given the system and PV will be connected via a switch,
>>> what needs to be done to make sure the Networker server can see and
use
>>> the PV and its drive?
>>>
>>> -Brian
>>>
>>> --
>>> Note: To sign off this list, send a "signoff networker" command via
>>> email
>>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>>> http://listmail.temple.edu/archives/networker.html where you can
>>> also view and post messages to the list. Questions regarding this
list
>>> should be sent to stan AT temple DOT edu
>>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>
> --
> Note: To sign off this list, send a "signoff networker" command via
email
> to listserv AT listmail.temple DOT edu or visit the list's Web site at
> http://listmail.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via
email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=