First time posting, sorry for the long story..
I have been running a configuration of 1 master server with 1 tape
library and 1 NDMP server/client (the Auspex) for about 2 years
now without too many problems. The master is a Sun Ultra II at
Solaris 2.5.1, Veritas NetBackup at 3.2 with veritas jumbo patch
patchJ0800168 and patchJ0800167 installed. NDMP was a bit tricky
but it works fine now. We had Veritas support then, We have SUN
now..
I am adding a media slave server (SUN Ultra II, Sol7) with a L11000
tape library. I had alot of problems with the st.conf file on the
slave server. Tho' I think that has been resolved.
Moving right along with the configuration, I did all the steps in the
MM Device Config Guide (UNIX) for configuring the SG driver...,
Then, on the Slave server, I configured the robotics and drives
in the xdevadm Xwindow. Took the default robot 0, (tho I have
tried robot #3 as well since I already have 0,1 & 2 on the master, but
I'm not sure of the connections with the robot numbers).. Added the
drives as robotic, for robot #0.. then restarted the device daemon on
the slave.
On the master, I also added the robot and drives. The robot came up
as robot #3. My messages in /var/adm/messages on both the master and
the slave complain about each other. I've used full name for the
slave on the master in the storage unit, and the device mgr robot
configuration page. Still I get these errors:
SLAVE:
shahna [root] tail /var/adm/messages
Oct 11 12:29:07 shahna tldcd[394]: Unknown robot number 3, from host
crusher.wv.tek.com
Oct 11 12:35:26 shahna tldd[3838]: Device=0, TLD=0, DRIVE=1
Oct 11 12:35:26 shahna tldd[3838]: Device=1, TLD=0, DRIVE=2
Oct 11 12:35:26 shahna tldcd[3842]: Daemon is already initiated
Oct 11 12:35:32 shahna tldd[3838]: DecodeQuery() Actual status: STATUS_SUCCESS
Oct 11 12:35:32 shahna tldd[3838]: TLD(0) going to UP state
Oct 11 12:35:32 shahna ltid[3830]: Received Type=2 message from TLD(0),
RobotConnect
continuing
Oct 11 12:36:06 shahna tldcd[394]: Unknown robot number 3, from host
crusher.wv.tek.com
MASTER:
Oct 11 12:46:30 crusher tldd[5088]: TLD(3) unavailable: initialization failed:
Robot
number does not exist
Oct 11 12:32:15 crusher avrd[5089]: Fatal open error on s1drive0 (device 8,
/devices/sbus@1f,0/SUNW,fas@0,8800000/sg@0,0:raw), errno = 19 (No such device),
DOWN'ing
it
Oct 11 12:48:32 crusher tldd[5088]: TLD(3) unavailable: initialization failed:
Robot
number does not exist
bpadm -> storage unit -> list gives this:
Label: crusher_r2d2
Storage Unit Type: Media Manager
Host Connection: crusher
Number of Drives: 4
On Demand Only: no
Max MPX/drive: 20
Density: dlt - DLT Cartridge
Robot Type/Number: TLD / 0
Max Fragment Size: (unlimited)
Label: dodona_c3po
Storage Unit Type: NDMP
Host Connection: crusher
Number of Drives: 2
On Demand Only: yes
Max MPX/drive: 1
Density: dlt - DLT Cartridge
Robot Type/Number: TLD / 2
Max Fragment Size: (unlimited)
NDMP attach host: dodona38
Label: optical
Storage Unit Type: Media Manager
Host Connection: crusher
Number of Drives: 2
On Demand Only: no
Max MPX/drive: 1
Density: odiskwm - Optical Disk Write-Many
Robot Type/Number: ODL / 1
Max Fragment Size: (unlimited)
Label: shahna_gort
Storage Unit Type: Media Manager
Host Connection: shahna.wv.tek.com
Number of Drives: 2
On Demand Only: no
Max MPX/drive: 20
Density: dlt - DLT Cartridge
Robot Type/Number: TLD / 3
Max Fragment Size: (unlimited)
Any hints, tips, or ideas?
Thanks.
jann
=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-
=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-
= Jann Ryan E-mail: Jann.Ryan AT opbu.xerox DOT com
= OPBU System Administration Voice: (503) 685-3642
= m/s 61-001 FAX: (503) 685-3880
= PO BOX 1000
= Wilsonville OR 97070-1000
=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-
=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-=~=-
|
