Operating System - HP-UX
1834796 Members
2746 Online
110070 Solutions
New Discussion

Ignite Backup Failed complete

 
James_343
New Member

Ignite Backup Failed complete

Received the followning information in the maketape.log file.

Recovery Archive Location =
6 REPLIES 6
Helen French
Honored Contributor

Re: Ignite Backup Failed complete

Are you doing a local Ingnite backup or remote backup? In any case, did you specify the destination location:

-a /dev/rmt/0mn
OR
-a hostname:location
Life is a promise, fulfill it!
James_343
New Member

Re: Ignite Backup Failed complete

The command that gets run is the following. This is the one thats been working all along. Weather the parms your mention get run during the execution of the ignite command below, I'm not sure. FYI, some pathces were applied before the this last backup was run.

sudo /opt/ignite/bin/make_tape_recovery -vI -x inc_entire=vg00 | tee -a $logfile.
Helen French
Honored Contributor

Re: Ignite Backup Failed complete

Add the option -a with your command:

# make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/?mn

/dev/rmt/?mn should be your tape drive location where you have the recovery tape installed. Check available device names from:

# ioscan -fnkC tape
Life is a promise, fulfill it!
James_343
New Member

Re: Ignite Backup Failed complete

We have this same mechanism in place and working on another system without defining the tape device and -a flag within the the sudo command. Is this simply a work around to get Ignite to see the drive is another patch required to fix the problem?

Thx


Helen French
Honored Contributor

Re: Ignite Backup Failed complete

That's true, even if you don't specify -a option with the tape device file, the system will take the default one that is /dev/rmt/0mn. Now, if you have changed the device file or tape drive or the SCSI ID recenly, then your device file also can change from /dev/rmt/0mn to 1mn or 2mn etc. Otherwise you should specify your default device on /var/opt/ignite/recovery/dafault file.

Now, to make sure all these, check your tape device files with the ioscan command I posted and make sure you are doing it right.

Also, if you haven't changed any of these in your system recently, there is a strong chance that a system patch will rectify these issues. Make sure you do a custom patch analysis and install your patches as well.
Life is a promise, fulfill it!
James_343
New Member

Re: Ignite Backup Failed complete

The Ignite backup has failed again. Please note the Recovery Archive setting "^P". it should read /dev/rmt/0mn. As idicated ealier, were running the same config in our Production environment and its working fine,

on May 10 19:28:51 EDT 2004
* Creating local directories for configuration files and archive.

======= 05/10/04 19:28:51 EDT Started /opt/ignite/bin/make_tape_recovery.
(Mon May 10 19:28:51 EDT 2004)
@(#) Ignite-UX Revision B.3.3.116
@(#) net_recovery (opt) $Revision: 10.543 $

* Testing pax for needed patch
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = ^P

* Number of Archives to Save = -1


ingxdev:/usr/local/logs# ioscan -fnkC tape
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/6/0/1.3.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/0m /dev/rmt/c7t3d0BEST
/dev/rmt/0mb /dev/rmt/c7t3d0BESTb
/dev/rmt/0mn /dev/rmt/c7t3d0BESTn
/dev/rmt/0mnb /dev/rmt/c7t3d0BESTnb