- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Where to point make_tape_recovery to changed HW in...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:38 PM
03-07-2003 01:38 PM
Where to point make_tape_recovery to changed HW instance No.?
System Recovery Archive
* Checking Versions of Ignite-UX filesets
Hello,
partly for cosmetic reason, partly in hope to satisfy OmniBack I changed a couple of HW instance Nos. to make device files look the same on all cluster nodes.
I used the "ioinit -f" procedure in runlevel 1 to this end.
Although this worked as expected it haunted me back when I wanted to make_tape_recovery of the freshly configured cluster node.
It rightly complains about a tape device misnomer:
ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.
======= 03/07/03 22:25:08 MET make_tape_recovery completed unsuccessfully
Hm, I modified hw.info to suite the new instance No.
# grep ext_bus /var/opt/ignite/local/hw.info
ext_bus: 0/0/1/0 3 c720 n/a SCSI_C895_Ultra_Wide_LVD
ext_bus: 0/0/2/0 1 c720 n/a SCSI_C87x_Ultra_Wide_Single-Ended
ext_bus: 0/0/2/1 2 c720 n/a SCSI_C87x_Ultra_Wide_Single-Ended
# ioscan -knfCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/c3t1d0BEST /dev/rmt/c3t1d0DDS
/dev/rmt/c3t1d0BESTb /dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0BESTn /dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0BESTnb /dev/rmt/c3t1d0DDSnb
# ioscan -kfCext_bus -H 0/0/1
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 3 0/0/1/0 c720 CLAIMED INTERFACE SCSI C895 Ultra Wide LVD
but it still croaks :-(
Who knows where instead to register the new tape device file to satisfy make_tape_recovery?
Rgds.
Ralph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:40 PM
03-07-2003 01:40 PM
Re: Where to point make_tape_recovery to changed HW instance No.?
Looks I had a copy'n'paste synchronity loss here ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:43 PM
03-07-2003 01:43 PM
Re: Where to point make_tape_recovery to changed HW instance No.?
You can specify '-a /dev/rmt/c3t1d0BESTn' with your 'make_tape_recovery' command.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:45 PM
03-07-2003 01:45 PM
Re: Where to point make_tape_recovery to changed HW instance No.?
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:55 PM
03-07-2003 01:55 PM
Re: Where to point make_tape_recovery to changed HW instance No.?
and then re-create using insf -H command
then check the device name for tape
then make_recovery -A -d /dev/rmt/Xmn
This should work....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2003 01:57 PM
03-07-2003 01:57 PM
Re: Where to point make_tape_recovery to changed HW instance No.?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2003 01:19 AM
03-10-2003 01:19 AM
Re: Where to point make_tape_recovery to changed HW instance No.?
Of course did I find out about the -a switch to feed make_tape_recovery with a preffered device.
But this wasn't the way I wanted it because I realized that my installation lacked the default tape device files.
The ordinary "insf -d stape -e" didn't create them for me.
It took quite some experimenting until I found out, by scrutiny of what lssf dumped on another box that had those files, viz.:
# lssf /dev/rmt/0m*
stape card instance 3 SCSI target 0 SCSI LUN 0 at&t best density available at ad
dress 0/0/2/1.0.0 /dev/rmt/0m
stape card instance 3 SCSI target 0 SCSI LUN 0 berkeley best density available a
t address 0/0/2/1.0.0 /dev/rmt/0mb
stape card instance 3 SCSI target 0 SCSI LUN 0 at&t no rewind best density avail
able at address 0/0/2/1.0.0 /dev/rmt/0mn
stape card instance 3 SCSI target 0 SCSI LUN 0 berkeley no rewind best density a
vailable at address 0/0/2/1.0.0 /dev/rmt/0mnb
that I needed to supply driver specific extra options when issuing the mksf command.
Finally that seemed to work:
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -a -b BEST /dev/rmt/0m
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -u -b BEST /dev/rmt/0mb
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -n -a -b BEST /dev/rmt/0mn
# mksf -I 0 -d stape -H 0/0/1/0.1.0 -n -u -b BEST /dev/rmt/0mnb
# ioscan -knfdstape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/0m /dev/rmt/c3t1d0BESTn
/dev/rmt/0mb /dev/rmt/c3t1d0BESTnb
/dev/rmt/0mn /dev/rmt/c3t1d0DDS
/dev/rmt/0mnb /dev/rmt/c3t1d0DDSb
/dev/rmt/c3t1d0BEST /dev/rmt/c3t1d0DDSn
/dev/rmt/c3t1d0BESTb /dev/rmt/c3t1d0DDSnb
# lssf /dev/rmt/0m*
stape card instance 3 SCSI target 1 SCSI LUN 0 at&t best density available at ad
dress 0/0/1/0.1.0 /dev/rmt/0m
stape card instance 3 SCSI target 1 SCSI LUN 0 berkeley best density available a
t address 0/0/1/0.1.0 /dev/rmt/0mb
stape card instance 3 SCSI target 1 SCSI LUN 0 at&t no rewind best density avail
able at address 0/0/1/0.1.0 /dev/rmt/0mn
stape card instance 3 SCSI target 1 SCSI LUN 0 berkeley no rewind best density a
vailable at address 0/0/1/0.1.0 /dev/rmt/0mnb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2003 03:25 AM
03-10-2003 03:25 AM
Re: Where to point make_tape_recovery to changed HW instance No.?
I'm sorry I couldn't have spelled it out more clearly for you. I've got the whole procedure written out step by step at work, but I answered from home and wasn't about to trust my crummy memory.
So, you're all set now?
Pete
Pete