make_tape_recovery issue

[Fauziah Mahdan]

Hi all,
I have 1 tape drive sharing with 3 servers.
When I move the tape drive into server c and run ioscan option appear as:
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/1/1.3.0 stape CLAIMED DEVICE HP C7438A
/dev/rmt/1m /dev/rmt/c3t3d0BESTnb
/dev/rmt/1mb /dev/rmt/c3t3d0DDS
/dev/rmt/1mnb /dev/rmt/c3t3d0DDSb
/dev/rmt/c3t3d0BEST /dev/rmt/c3t3d0DDSn
/dev/rmt/c3t3d0BESTb /dev/rmt/c3t3d0DDSnb
/dev/rmt/c3t3d0BESTn

When I perform make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/0m


error as

ERROR: This is not a no rewind device file.
ERROR: Check tape device failed.

The problem is I don't have option mn to choose.
Pls help.

[Avinash20]

Try this,

# mkdir /tmp/tape_backup
# mv /dev/rmt/* /tmp/tape_backup
# insf -e
# ioscan -fn tape

>> Try taking ignite backup

[smatador]

Hi,
Maybe is a typo, but the ioscan show the 1m tape and you perform a tape_recovery on the 0m tape.
So if you want to reinstall tape driver do what avinash write, but first check if you have the no rewind driver ll /dev/rmt/*mn

[Ganesan R]

Hi,

It is always preferred to connect the tape drives when the system is powered off. If we connect the drive online then kernel may not detect the drive and leads into many issues.

First thing you need to try is reboot the system and check if all the required device files are created.

Remove the device files at hardware path 0/1/1/1.3.0 and recreate it.

#rmsf -H 0/1/1/1.3.0
#insf -e -v

[Steven E. Protter]

Shalom,

Make sure the tape drive has power and scsi.

insf -e

Try again

SEP

[Fauziah Mahdan]

Agreed that I ahve connected to the tape drive during server on.
But I have restarted the server.
BTW I run

rmsf -H 0/1/1/1.3.0
# insf -e
insf: Installing special files for sdisk instance 0 address 0/0/2/0.0.0.0
insf: Installing special files for sctl instance 0 address 0/0/2/0.0.7.0
insf: Installing special files for sctl instance 1 address 0/0/2/0.1.7.0
insf: Installing special files for sdisk instance 1 address 0/1/1/0.0.0
insf: Installing special files for sdisk instance 2 address 0/1/1/0.1.0
insf: Installing special files for sctl instance 2 address 0/1/1/0.7.0
insf: Installing special files for sctl instance 3 address 0/1/1/1.7.0
insf: Installing special files for asio0 instance 0 address 0/6/1/0
insf: Installing special files for asio0 instance 1 address 0/6/1/1
insf: Installing special files for ipmi instance 0 address 250/0
insf: Installing special files for asio0 instance 2 address 250/1
insf: Installing special files for asio0 instance 3 address 250/2
insf: Installing special files for pseudo driver cn
insf: Installing special files for pseudo driver mm
insf: Installing special files for pseudo driver udp
insf: Installing special files for pseudo driver ptym
insf: Installing special files for pseudo driver ptys
insf: Installing special files for pseudo driver tcp
insf: Installing special files for pseudo driver rawip
insf: Installing special files for pseudo driver nuls
insf: Installing special files for pseudo driver ip
insf: Installing special files for pseudo driver arp
insf: Installing special files for pseudo driver dmem
insf: Installing special files for pseudo driver tlcotsod
insf: Installing special files for pseudo driver tlcots
insf: Installing special files for pseudo driver tlclts
insf: Installing special files for pseudo driver devkrs
insf: Installing special files for pseudo driver dmp
insf: Installing special files for pseudo driver dev_config
insf: Installing special files for pseudo driver strlog
insf: Installing special files for pseudo driver sad
insf: Installing special files for pseudo driver stcpmap
insf: Installing special files for pseudo driver tels
insf: Installing special files for pseudo driver telm
insf: Installing special files for pseudo driver vols
insf: Installing special files for pseudo driver asyncdsk
insf: Installing special files for pseudo driver echo
insf: Installing special files for pseudo driver dlpi
insf: Installing special files for pseudo driver ptm
insf: Installing special files for pseudo driver pts
insf: Installing special files for pseudo driver klog
insf: Installing special files for pseudo driver sy
insf: Installing special files for pseudo driver kepd
insf: Installing special files for pseudo driver diag2
insf: Installing special files for pseudo driver root
# ioscan -fnCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/1/1.3.0 stape CLAIMED DEVICE HP C7438A


That the only result appear.

[smatador]

What's happen now with
make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/1mn

[Patrice Le Guyader]

hello,

I agree with smatador. You wrote :

"
/dev/rmt/1m /dev/rmt/c3t3d0BESTnb
/dev/rmt/1mb /dev/rmt/c3t3d0DDS
/dev/rmt/1mnb /dev/rmt/c3t3d0DDSb
/dev/rmt/c3t3d0BEST /dev/rmt/c3t3d0DDSn
/dev/rmt/c3t3d0BESTb /dev/rmt/c3t3d0DDSnb
/dev/rmt/c3t3d0BESTn

When I perform make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/0m
"

Where do you see a device file /dev/rmt/0m and so on ?

Hope this helps.
Kenavo
Pat

[Fauziah Mahdan]

as I said after remove the software and rerun insf
Check the ioscan
that the onlyr esult appear without all the

/dev/rmt/1m /dev/rmt/c3t3d0BESTnb
/dev/rmt/1mb /dev/rmt/c3t3d0DDS
/dev/rmt/1mnb /dev/rmt/c3t3d0DDSb
/dev/rmt/c3t3d0BEST /dev/rmt/c3t3d0DDSn
/dev/rmt/c3t3d0BESTb /dev/rmt/c3t3d0DDSnb
/dev/rmt/c3t3d0BESTn

only

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/1/1.3.0 stape CLAIMED DEVICE HP C7438A

appear.

Make_tape_recovery still not work

[sujit kumar singh]

Hi Fauziah,

if you are using this command #make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/0m

then the Ignite shall not occur because /dev/rmt/0m device-file is no more present on the system.


Instead use this command after you have loaded a media in the tape drive.

1)load the media in the tape drive properly.Wait for the Media to be stable after load and the green LED has stabilised.
2)Give the following command
#make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/1mn

the reason is that the tape drive in the system now shows that this device is /dev/rmt/1mn and no more as /dev/rmt/0m.



hope i am able to point you out that correctly

regards
sujit

[Patrick Wallek]

What you need to do is use '/dev/rmt/c3t3d0DDSn'. That is the equivalent of the '1mn' device.

You command should look like this:

make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/c3t3d0DDSn

[sujit kumar singh]

hi


please post the O/P of

#ll /dev/rmt


regards
sujit

[Avinash20]

Hi,

As I suggested

# mkdir /tmp/tape_backup
# mv /dev/rmt/* /tmp/tape_backup
# insf -e
# ioscan -fnC tape

[Avinash20]

From the ioscan output, after doing rmsf there are no device files available now, but the tape is CLAIMED in ioscan

Try the above commands and let me know.

I am trying to backup all the device file in /dev/rmt and then running insf to recreate the device file

Best of Luck !!

[Fauziah Mahdan]

HI all,

Since I only have this option I can't perform the make_tape_recovery

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/1/1.3.0 stape CLAIMED DEVICE HP C7438A
so I rerun another round of insf -e -v

So latest result it appear

ioscan -fnCtape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 1 0/1/1/1.3.0 stape CLAIMED DEVICE HP C7438A
/dev/rmt/1m /dev/rmt/c3t3d0BESTnb
/dev/rmt/1mb /dev/rmt/c3t3d0DDS
/dev/rmt/1mnb /dev/rmt/c3t3d0DDSb
/dev/rmt/c3t3d0BEST /dev/rmt/c3t3d0DDSn
/dev/rmt/c3t3d0BESTb /dev/rmt/c3t3d0DDSnb
/dev/rmt/c3t3d0BESTn

without /dev/rmt/1mn

so I perform this command
make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/c3t3d0DDSn.
Looks like it running now at stage

WARNING: You are about to create an Itanium-based recovery tape. To recover
the system using this tape, you must perform 'two-step media recovery'
where the boot media (CD or DVD) has the same version of Ignite-UX as
the version on this tape.
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/c3t3d0DDSn -t
n -s local -n 2009-02-11,08:31 -m t -w
/var/opt/ignite/recovery/2009-02-11,08:31/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-02-11,08:31/flist -a 39055440

* Preparing to create a system archive.

* Archiving contents of cgc_uat via tar image to local device/dev/rmt/c3t3d0DDSn.

[Dennis Handly]

>Since I only have this option I can't perform the make_tape_recovery
> WARNING: You are about to create an Itanium-based recovery tape.

What option? If you have the latest firmware, you can boot directly from tape.

[Armin Kunaschik]

This is right. Some itanium firmware releases are not able to boot from tape!

I'd suggest to use make_net_recovery, setting up an ignite server and install/maintain/recover over lan!

My 2 cents,
Armin

[Ganesan R]

Hi Fauziah,

If you still need /dev/rmt/1mn file, you can manually create it. It should use the same major and minor numbers of /dev/rmt/c3t3d0BESTn or /dev/rmt/c3t3d0DDSn.

#mknod /dev/rmt/1mn c 205 0x033040

ownership should be bin:bin

[Fauziah Mahdan]

hi all,
Need ur advice when I perform make_tape_recovery it require 2nd tape then error appear after inserting new tape and press 'go'.


pax: opt/IBM/WebSphere/AppServer/systemApps/adminconsole.ear/adminconsole.war/WEB-INF/classes/_ibmjsp/com_2E_ibm_2E_ws_2E_console_2E_sibws_2E_sibusresources_2E_wss/_SIBWSSecurityServiceConfigsSummary.class : Path name element too long - skipped
pax: Ready for volume 2 go
pax: Ready for volume 2dy to proceed (or "quit" to abort):
pax: Type "go" when ready to proceed (or "quit" to abort): go
Continuing
WARNING: The pax command returned a non-zero exit status (exit status 1).
* Creation of system archive complete.

NOTE: Could not read the /etc/resolv.conf file.
* Cleaning up old configuration file directories

======= 02/11/09 13:31:13 PST make_tape_recovery completed with warnings
#

[OldSchool]

looks like you may have way more than the base OS installed in vg00.

my suggestion would be to look at /opt and identify any directories (such as /opt/IBM) that don't need to be on the ignite image. include all of vg00 and exclude the non-essential bits. those can be part of another backup tape (tar, dp or whatever)

something like:

make_tape_recovery -v -I -x inc_entire=vg00 -a /dev/rmt/c3t3d0DDSn -x exclude=/opt/IBM -x exclude=.......

[Avinash20]

The following file opt/IBM/WebSphere/AppServer/systemApps/adminconsole.ear/adminconsole.war/W
EB-INF/classes/_ibmjsp/com_2E_ibm_2E_ws_2E_console_2E_sibws_2E_sibusre
sources_2E_wss/_SIBWSSecurityServiceConfigsSummary.class is longer than 255 char

Also this is not an OS file.
Ignite is only recommended for HP-UX OS

You could take the backup of /opt/IBM via fbackup after ignite backup is taken

Above command posted(
-exclude=/opt/IBM) will exclude the /opt/IBM