Hi Jerome,
So we are not alone!!! We have the same thing with NB 3.4 on a
single Solaris 8 server, an L700 and LTO fiber channel drives. It's
been really annoying to say the least.
We're thinking of writing a script to link the devices in the same way
every time, but we can't believe that this is what we should be doing.
We are using Netbackup 3.4 patched to NB_34_3 on a Sun V880 running
Solaris 8.
Server is up-to-date with patches.
Library is an HP 20/700, Model number A5597A and is at firmware revision
3.01.02
Drive are HP LTO/Utrium 1 SCSI Model A6323A with firmware E258/005.485
(Actually we've had some replaced, so we have a mix of drive firmware
temporarily.)
Bridges are HP Model A4688A with firmware 2008e
The HBAs in the Sun server are two single PCI FC adapters Sun option
#X6799A
(Top Level # 595-5830; Mfg # 375-3019; with the ISP 2200 chip)
I'd be really interested in hearing from people who have something like
this working!
Thanks very much in advance....Gerrit
jerome bauwens wrote:
> Hi, I'm using a NB 3.4 on 2 solaris servers with a L700 library and
> 9840 fiber channel drives. My drive configuration were resetted on a
> media server this weekend for the second time in a week and it pisses
> me off. [athena]:/usr/openv/netbackup/db/media>tpconfig -d
>
> Index DriveName DrivePath Type Multihost Status
>
> ***** ********* ********** **** ********* ******
>
> 0 STK98402 /dev/rmt/0cbn hcart No UP
>
> TLD(0) Definition DRIVE=1 <-------- should be drive 3
>
> 1 STK98403 /dev/rmt/1cbn hcart No UP
>
> TLD(0) Definition DRIVE=4
>
> Currently defined robotics are:
>
> TLD(0) robot host = zeus, volume database host = zeus
>
>
>
> The TLD definition for the STK98402 drive was DRIVE=3 last week and it
> just changed during the weekend causing the drive to go down and
> multiple jobs to fail as every request that should have been made to
> this drive were made to the STK98400 (DRIVE=1) on the other media
> server but failed as the drive was already used (I don't even think it
> would have worked even if the drive had not been used). My first
> question is: has anybody seen this? My second is: How do you reset it
> using command lines (tpconfig doesn't) ?
>
> Besides, a signal 15 seemed to cause the process to restart on both
> the master and media:
>
> file messages on the master (also media server for 4 drives):
>
> Nov 9 14:27:15 zeus ltid[7769]: [ID 429237 daemon.notice] LTID -
> received ROBOT MESSAGE, Type=54, LongParam=0, Param1=1, Param2=0
>
> Nov 9 15:02:19 zeus vmd[21335]: [ID 631293 daemon.notice] terminating
> - successful (0)
>
> Nov 9 15:02:34 zeus tldcd[7975]: [ID 459737 daemon.error] Daemon has
> terminated due to signal (15)
>
> Nov 9 15:02:34 zeus ltid[7769]: [ID 394161 daemon.error] LTID
> terminating because it received a signal (15)
>
> Nov 9 15:02:36 zeus ltid[7769]: [ID 265732 daemon.warning] Sending
> shutdown to tldcd daemon...
>
> Nov 9 15:04:09 zeus vmd[16381]: [ID 734361 daemon.notice] ready for
> connections on socket 2
>
> Nov 9 15:04:13 zeus tldd[16546]: [ID 754584 daemon.notice] Device=0,
> TLD=0, DRIVE=1
>
> Nov 9 15:04:13 zeus tldd[16546]: [ID 820121 daemon.notice] Device=1,
> TLD=0, DRIVE=2
>
> Nov 9 15:04:13 zeus tldd[16546]: [ID 951196 daemon.notice] Device=3,
> TLD=0, DRIVE=5
>
> Nov 9 15:04:13 zeus tldd[16546]: [ID 116752 daemon.notice] Device=4,
> TLD=0, DRIVE=6
>
> Nov 9 15:04:13 zeus tldcd[16569]: [ID 617824 daemon.notice] Ready for
> connections
>
> file messages on the media server which lost its configuration :
>
> Nov 9 14:58:05 athena vmd[11698]: [ID 631293 daemon.notice]
> terminating - successful (0)
>
> Nov 9 14:59:10 athena vmd[2226]: [ID 734361 daemon.notice] ready for
> connections on socket 2
>
> Nov 9 14:59:14 athena tldd[2405]: [ID 754584 daemon.notice] Device=0,
> TLD=0, DRIVE=1 <-- should be 3
>
> Nov 9 14:59:14 athena tldd[2405]: [ID 820123 daemon.notice] Device=1,
> TLD=0, DRIVE=4
>
> Nov 9 14:59:29 athena tldd[2409]: [ID 801976 daemon.error] TLD(0)
> [2409] unable to connect to tldcd on zeus: Connection refused (14
>
> 6)
>
> Nov 9 14:59:29 athena tldd[2405]: [ID 560769 daemon.notice]
> DecodeQuery() Actual status: Control daemon connect or protocol error
>
> Nov 9 14:59:29 athena tldd[2405]: [ID 181918 daemon.error] TLD(0)
> unavailable: initialization failed: Control daemon connect or pro
>
> tocol error
>
> Nov 9 15:01:31 athena tldd[2405]: [ID 885524 daemon.notice]
> DecodeQuery() Actual status: STATUS_SUCCESS
>
>
>
> The time difference is due to the actual time difference between the
> two servers.
>
> Help will be greetly appreciated,
>
> Jerome.
|
