Veritas-bu

[Veritas-bu] Netbackup Not Seeing My Tape Drive

2003-10-02 14:15:52
Subject: [Veritas-bu] Netbackup Not Seeing My Tape Drive
From: PAkre AT JNI DOT com (Pete Akre)
Date: Thu, 2 Oct 2003 11:15:52 -0700
Thanks for the info, I sure am learning alot. But mine show as: 0cbn ->
../../devices/pci@1f,2000/SUNW,jfca@1,1/fp@0,0/st@w500507630061254d,0:cbn.
So how would I setup my conf files to handle this weird number? Would I just
make the target w500507630061254d? Is that even valid?

Thanks

Peter Akre

-----Original Message-----
From: Darren Dunham [mailto:ddunham AT taos DOT com]
Sent: Thursday, October 02, 2003 11:07 AM
To: Pete Akre
Subject: Re: [Veritas-bu] Netbackup Not Seeing My Tape Drive


> 
> Here's another ignorant question. How do I know what target address to use
> for this tape drive? I have arbitrarily created entries from 0-20 with no
> effect.

That depends on your connection adapter and the driver.

For a scsi drive, the adapter will map the scsi target to the t# in the
device path.

For a fiber adapter, the adapter has several choices, but generally it
will map a single fiber WWPN to a target number.  The driver can usually
do it dynamically (pick a low number), or staticly (create an explicit
mapping within the driver configuration file).

However, you say you already see (and can access) the devices via
/dev/rmt/*.  Just do an expansion of one of them..

lrwxrwxrwx   1 root     root          45 Mar 11  2003 /dev/rmt/8cbn ->
../../devices/pci@6,2000/JNI,FCE@1/st@2,0:cbn

The "@2" means that this particular drive is on target 2 for this
adapter.


-- 
Darren Dunham                                           ddunham AT taos DOT com
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >