[Veritas-bu] We recabled Drives and now we have problems
2001-06-19 20:04:45
Subject: |
[Veritas-bu] We recabled Drives and now we have problems |
From: |
tallen201 AT hotmail DOT com (Tim Allen) |
Date: |
Tue, 19 Jun 2001 20:04:45 -0400 |
Hello.
I'm using NetBackup 3.2 on an E250 Master and an E450 media server.
We replaced a a bad SCSI cable and recabled so that there are two drives per
adapter. The robot and two drives were on the same adapter, and we placed
the tow drives on there own adapter.
The drives are noticed with sgscan, but I didn't change anything in the
config since the drives were still associated with the same /dev/rmt/#.
Should I have removed them and readded them anyway?
Media server:
/dev/sg/c3t4l0: Tape (/dev/rmt/0): "QUANTUM DLT7000"
/dev/sg/c3t5l0: Tape (/dev/rmt/1): "QUANTUM DLT7000"
/dev/sg/c5t2l0: Tape (/dev/rmt/2): "QUANTUM DLT7000"
/dev/sg/c5t3l0: Tape (/dev/rmt/3): "QUANTUM DLT7000"
/dev/sg/c6t4l0: Tape (/dev/rmt/4): "QUANTUM DLT7000" -added drive to config
/dev/sg/c6t5l0: Tape (/dev/rmt/5): "QUANTUM DLT7000" -added drive to config
Master: new
/dev/sg/c2t2l0: Tape (/dev/rmt/0): "QUANTUM DLT7000"
/dev/sg/c2t3l0: Tape (/dev/rmt/1): "QUANTUM DLT7000"
/dev/sg/c5t0l0: Changer: "ATL P3000 6310070"
The following are the errors thar are seen when a backup is attempted.
Jun 19 17:42:21 Master last message repeated 1 time
Jun 19 17:42:21 Master tldd[1282]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:43:29 Master tldcd[1286]: TLD(0) Library communications
established, but no drives in library
Jun 19 17:44:24 Master last message repeated 1 time
Jun 19 17:44:24 Master tldd[1282]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:45:32 Master tldcd[1286]: TLD(0) Library communications
established, but no drives in library
Jun 19 17:46:27 Master last message repeated 1 time
Jun 19 17:46:27 Master tldd[1282]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:47:35 Master tldcd[1286]: TLD(0) Library communications
established, but no drives in library
--
Jun 19 17:40:25 MediaServer tldd[2218]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:44:31 MediaServer last message repeated 2 times
Jun 19 17:46:34 MediaServer tldd[2218]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:52:43 MediaServer last message repeated 3 times
Jun 19 17:54:46 MediaServer tldd[2218]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
Jun 19 17:58:52 MediaServer last message repeated 2 times
Jun 19 18:00:55 MediaServer tldd[2218]: TLD(0) unavailable: initialization
failed: Unable to initialize robot
The backups failed with error 54.
The bprd logs on the MediaServer show
17:30:11 [2212] <2> hosts_equal: hostnames DO NOT compare
17:30:11 [2212] <2> hosts_equal: name1=MediaServer name2=MasterServer
17:30:11 [2212] <2> hosts_equal: hostbuf=MediaServer.Domain
hostentry->h_name=MasterServer.Domain
17:30:11 [2212] <2> hosts_equal: compare MediaServer.Domain with alias
MasterServer
17:30:11 [2212] <2> hosts_equal: compare MasterServer.Domain with alias
MediaServer
17:30:11 [2212] <2> hosts_equal: compare MasterServer.Domain with alias
loghost
17:30:11 [2212] <2> hosts_equal: addresses DO NOT match
17:30:11 [2212] <4> hosts_equal: MediaServer=0xa0a1472
MasterServer=0xa0a1471
Nothing was changed in the bp.confs or /etc/hosts.
I'm sending this out in case someone else has an idea of where I should look
next.
Thanks.
Tim
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Veritas-bu] We recabled Drives and now we have problems,
Tim Allen <=
|
|
|