In addition to Judy's email:
It seems as if someone has opened the library door and manually added
tapes while tapes were mounted in the drives - when the tapes needed to
be put back in their original slots, it found another tape there.
About your 83's:
Everything in your environment seems to be VERY OLD. How old is the
media? Do 'vmquery -m 'media-id' tapes giving status 83. When was the
media added? How many times has it been mounted?
Another possibility is your st driver - check the patch level as well as
st.conf entry. NetBackup 3.4 came with a full set of manuals - find your
Media Manager Device Configuration Guide. Check the Solaris chapter for
recommended st.conf entries for your tape drives.
Another manual in your set is the Troubleshooting Guide. It explains in
detail why you are getting this error, possible reasons and what to
check. One of the logs to check is the bptm log on the media servers.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of bkpguy
Sent: 26 February 2009 16:22
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Crazy at Errors in Netbackup 3.4 on Solaris 7
Hi Gents,
Need your kind help/advise/instructions to cure my big problems in
netbackup server3.4 running on solaris7 and overland tape library . I
have one netbackup 3.4 server and a few media servers running under it.
I used to received status code 83 from the backup of media tapes under
one of the media servers . I suspect it is due to media tape errors and
I changed the tapes under this media server group. But other media tapes
under another media server also came out status code 83 and a lot of
errors as per follows. PLS PLS HELP ME OUT FROM THIS TROUBLE SINCE I M
GOING TO CRAZY.
#more /var/adm/messages
Feb 26 09:55:52 netbkpserver002 tldcd[22074]: TLD(2) key = 0x0, asc =
0x0, ascq = 0x0, NO ADDITIONAL SENSE INFORMATION
( It is due to backup tape library ? Pls.advise )
Feb 26 09:55:52 netbkpserver002 tldcd[22074]: TLD(2) Move_medium error:
CHECK CONDITION
( Really due to media error ? )
Feb 26 10:02:25 netbkpserver002 tldcd[22386]: TLD(2) cannot dismount
drive 2, slot 91 already is full
Feb 26 10:02:25 netbkpserver002 tldcd[22386]: TLD(2) key = 0x0, asc =
0x0, ascq = 0x0, NO ADDITIONAL SENSE INFORMATION
Feb 26 10:02:25 netbkpserver002 tldcd[22386]: TLD(2) Move_medium error:
CHECK CONDITION
-Feb 26 10:19:55 netbkpserver002 tldcd[22962]: TLD(2) expected barcode
(media03 ) in slot 85, found barcode (--------)
Feb 26 10:23:42 netbkpserver002 tldcd[23000]: TLD(2) expected barcode
(media03 ) in slot 85, found barcode (media01 )
Feb 26 10:27:28 netbkpserver002 tldcd[23034]: TLD(2) expected barcode
(media03 ) in slot 85, found barcode (media01 )
Feb 26 10:28:13 netbkpserver002 tldcd[23055]: TLD(2) expected barcode
(media03 ) in slot 85, found barcode (media01 )
( Volume database is not update with physical media location , Pls.
advise , it happen automatically )
Feb 26 10:30:19 netbkpserver002 tldcd[23222]: TLD(2) cannot dismount
drive 2, slot 91 already is full
[size=18]Feb 26 10:31:48 netbkpserver002 ID[RICHPse.monlog.2000]: Disk
state amber entered, Action: Move load from busy disks to idle disks
Feb 26 10:33:48 netbkpserver002 ID[RICHPse.monlog.2000]: Disk state
white entered, Action: No activity[/size]
( I have no idea about the disk state amber and white , what does it
mean ? )
Feb 26 20:14:50 netbkpserver002 tldd[2402]: TLD(2) drive 1 (device 0) is
being DOWNED, status: Robotic mount failure
( The tape LTOD drives are keeping on down evey 5 to 10 minutes
eventhough I changed the tape library drives , why ?)
#more /usr/openv/netbackup/db/error
1235615750 1 4 16 production 26131 0 0 bkpwindowsATC001 bpsched backup
of client bkpwindowsATC001 exited with status 83 (media open error)
1235615750 1 4 16 netbkpserver002 0 0 0 *NULL* bpsched scheduler exiting
- media open error (83)
Robot inventory/ media database is not sync with the physical slots in
the tape library.
1235651678 1 4 4 netbkpserver002 0 0 0 netbkpserver002 bpsched skipping
backup of client netbkpserver002, class bkp_web2, schedule incrbkps
because it has exceeded the configured number of tries
1235651678 1 4 4 netbkpserver002 0 0 0 bkpunix006 bpsched skipping
backup of client bkpunix006, class bkp_web3, schedule incrbkps because
it has exceeded the configured number of tries
( Why so many tapes are not able to mount ? Drive error or media error ?
)
1235650486 1 132 16 netbkpserver002 26153 0 0 bkpClass bptm FREEZING
media id bkp02, it is unmountable and cannot be used for backups
1235650488 1 132 16 netbkpserver002 26153 0 0 bkpClass bptm FREEZING
media id bkp07, it is unmountable and cannot be used for backups
( the tapes are usually freeze every now and then , due to media tape
error ? )
************************************************************************
************************
more bpmedialist
Feb 26 20:14:52 netbkpserver002 vmd[2385]: media ID bkp04 has expired
Feb 26 20:14:52 netbkpserver002 vmd[2385]: media ID bkp05 has expired
Feb 26 20:14:58 netbkpserver002 vmd[2385]: media ID bkp04 has expired
Feb 26 20:14:58 netbkpserver002 vmd[2385]: media ID bkp05 has expired
( How can I use back those media to normal backup ? )
I really really really need your gentlemen help since I am getting a lot
of problems with this old backup 3.4 server . Pls. help me out.
Thanks
+----------------------------------------------------------------------
|This was sent by naymyo.tun AT bt DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
