fbackup on hpux 11.11 rp5470 after tape drive swap

[mike_s_brentlinger]

I had an ultrium-1 tape drive that went bad that i replaced with an ultrium-2 drive and everything seemed fine, but fbackup is now throwing errors. Im at a bit of a loss as to what to do. Are my tape drivers just confused somehow? Id like to not reboot the server but if I need to then so be it...

If someone could be so kind as to provide some insight I would greatly appreciate it. Thanks very much in advance.





here was my bad drive

# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 0 0/12/0/0.3.0 stape NO_HW DEVICE HP Ultrium 1-SCSI
/dev/rmt/0m /dev/rmt/0mn /dev/rmt/c5t3d0BEST /dev/rmt/c5t3d0BESTn
/dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c5t3d0BESTb /dev/rmt/c5t3d0BESTnb
# grep -i tape /var/adm/syslog/syslog.log lead me to
# /opt/resmon/bin/resdata -R 204734466 -r /storage/events/tapes/SCSI_tape/0_12_0_0.3.0 -n 204734468 -a
..
Event Time..........: Wed Dec 26 01:37:30 2007
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 100057
...
Summary:
Tape at hardware path 0/12/0/0.3.0 : Hardware failure
Description of Error:
The device was unsuccessful in processing the current I/O request due to
an internal target failure. The request may have been processed in a way
which could cause damage to or loss of data.





I powered off the bad drive, replaced it with an ultrium-2 and powered that drive up, then did
# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
tape 0 0/12/0/0.3.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/0m /dev/rmt/c5t3d0BEST
/dev/rmt/0mb /dev/rmt/c5t3d0BESTb
/dev/rmt/0mn /dev/rmt/c5t3d0BESTn
/dev/rmt/0mnb /dev/rmt/c5t3d0BESTnb
i didnt think i really needed to do this but just in case...
# insf -e
insf: Installing special files for btlan instance 0 address 0/0/0/0
...
...
...
then stuck in a tape and...
# mt -f /dev/rmt/0mn rew#
# mt -f /dev/rmt/0mn status
Drive: HP Ultrium 2-SCSI
Format:
Status: [41114000] BOT online compression immediate-report-mode
File: 0
Block: 0
# echo tape_test > tape_test
# cat tape_test
tape_test
# tar -cvf /dev/rmt/0m ./tape_test
a ./tape_test 1 blocks
# rm ./tape_test
# tar -tf /dev/rmt/0m
./tape_test
# tar -xvf /dev/rmt/0m
x ./tape_test, 10 bytes, 1 tape blocks
# cat ./tape_test
tape_test
#




everything seemed ok, but ever since fbackup fails with errors like the following. at first i thought it was the tape but ive tried multiple tapes
Output from fbackup:
br_backup: Invoking fbackup. See /var/sam/log/br_log for details.
fbackup(1004): session begins on Tue Jan 8 01:30:02 2008
fbackup(3203): volume 1 has been used 140 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/0m
fbackup(3026): ioctl error, can't query outfile
at media record 215360
fbackup(3102): attempting to make this volume salvagable
fbackup(3123): could not read the previous checkpoint record
fbackup(3105): writing 2 EOFs and rewinding the tape
fbackup(3106): please mount a good tape
fbackup(3038): output file /dev/rmt/0m is not a valid device file for backup
fbackup(3019): would you like to enter a new output file?
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit

[James R. Ferguson]

Hi Mike:

Make sure that you have patch PHKL_34552.

Regards!

...JRF...

[mike_s_brentlinger]

James, Thanks for the quick response.

it seems i dont have that patch installed...

# swlist -l product|grep -i PHKL_34552
#

from the install docs at
http://www11.itrc.hp.com/service/patch/patchDetail.do?patchid=PHKL_34552&sel={hpux:11.11,}&BC=main|search|
it seems to infer ill be needing a reboot to make it take affect and in fact it may reboot automatically if i use the steps provided?

step 5 ) Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_34552.depot

Would you agree on my assesment? If so perhaps ill wait till after hours to apply this one :)

thanks again

[James R. Ferguson · Accepted solution]

Hi (again) Mike:

Yes, the installation of PHKL_34552 will require a reboot.

Kernel patches are denoted with "KL"; Network related patches with "NE"; patches for commands with "CO" and those for other subsystems (e.g. compilers) with "SS".

Anytime you see "KL" or (generally) "NE" you know that a reboot will be required.

Regards!

...JRF...

[mike_s_brentlinger]

James
After itial testing that patch seemed to fix it... Ill re-enable my nightly backups and see what happens long term but I suspect itll be fine.

Thanks again.