1833872 Members
1729 Online
110063 Solutions
New Discussion

Re: Ignite Backup Failed

 
kevincho
Advisor

Ignite Backup Failed

Thank you always for ur helping.

System : rp3440
O/S : HPUX 11iV1
Ignite Ver : B.5.4.50

I'm about to back up with ignite but i've got some problem.

Plz look what i did.

prdldap2[/]# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/1/1/1.5.0 stape CLAIMED DEVICE HP C7438A
/dev/rmt/0m /dev/rmt/c3t5d0BESTn
/dev/rmt/0mb /dev/rmt/c3t5d0BESTnb
/dev/rmt/0mn /dev/rmt/c3t5d0DDS
/dev/rmt/0mnb /dev/rmt/c3t5d0DDSb
/dev/rmt/c3t5d0BEST /dev/rmt/c3t5d0DDSn
/dev/rmt/c3t5d0BESTb /dev/rmt/c3t5d0DDSnb
prdldap2[/]# swlist -l fileset |grep -i ignite
# Ignite-UX B.5.4.50 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL-PA B.5.4.50 Installation Boot Kernel for S700/S800 clients
Ignite-UX.BOOT-SERVICES B.5.4.50 Network Boot Services for System Installations
Ignite-UX.FILE-SRV-11-11 B.5.4.50 File Archives Used By Clients During HP-UX Install
Ignite-UX.IGNITE B.5.4.50 Graphical Ignite User Interface for Installations
Ignite-UX.IGNT-ENG-A-MAN B.5.4.50 Ignite-UX Manual Pages
Ignite-UX.MGMT-TOOLS B.5.4.50 Tools for Managing Data Files on an Ignition Server
Ignite-UX.OBAM-RUN B.5.4.50 User Interface Libraries Needed for Older Systems
Ignite-UX.RECOVERY B.5.4.50 System disaster recovery tools
prdldap2[/]# make_tape_recovery -Av -a /dev/rmt/0mn
* Creating local directories for configuration files and archive.

======= 02/23/07 11:06:42 KST Started make_tape_recovery. (Fri Feb 23
11:06:42 KST 2007)
@(#) Ignite-UX Revision B.5.4.50
@(#) net_recovery (opt) $Revision: 10.637 $

* Testing pax for needed patch
* Passed pax tests.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/defaults.

* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = cpio


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c2t0d0 /dev/dsk/c2t1d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
ERROR: Failed to open tape device /dev/rmt/0mn:No such device or address
(errno = 6).
ERROR: Check tape device failed.

======= 02/23/07 11:16:49 KST make_tape_recovery completed unsuccessfully

prdldap2[/var]# ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/1/1/1.5.0 stape NO_HW DEVICE HP C7438A
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c3t5d0BESTn /dev/rmt/c3t5d0DDSb
/dev/rmt/0mb /dev/rmt/c3t5d0BEST /dev/rmt/c3t5d0BESTnb /dev/rmt/c3t5d0DDSn
/dev/rmt/0mn /dev/rmt/c3t5d0BESTb /dev/rmt/c3t5d0DDS /dev/rmt/c3t5d0DDSnb

: Tape Decive is claimed as you can see.
But there is no such or device after issued command . i cannot understand this situation.

I tried something to solve this ploblem.

1. regenerate devie file with rmsf , insf
2. changed SCSI ID from 4 to 5
3. changed tape device


Isn't there anything else ?

Plz advice me ~!

Thanks in advance

Regards

John_cho
3 REPLIES 3
Patrick Wallek
Honored Contributor

Re: Ignite Backup Failed

If you look at your second ioscan ouput, you will notice that the device is in a NO_HW state. This means that the device is not accessible for some reason.

You need to investigate your tape drive and verify it really is working.
Fabian Briseño
Esteemed Contributor

Re: Ignite Backup Failed

I agree with patrick your second output states taht stape is in a NO_HW state.

Check you syslog.log file to see more info or run dmesg.


Knowledge is power.
YAQUB_1
Respected Contributor

Re: Ignite Backup Failed

Hi John_cho,

Good Morning...

I have gone through your mail. As per my knowledge its may be H/W issue. Below the guide line you follow:

1. Power off tape device.
2. Unplug SCSI cable and replace SCSI cable from systems to tape device.
3. Check the SCSI cable pine is break or not.
4. Tape device power up.
5. Logging the systems as a root user...
# ioscan
# ioscan -fnC tape
# make_tape_recovery -x inc_entire=vg00

I think it will help full to you.

Thansk-Yaqub.