Operating System - HP-UX
1837520 Members
3694 Online
110117 Solutions
New Discussion

Ignite backup failures, another scenario

 
SOLVED
Go to solution
Waqar Razi
Regular Advisor

Ignite backup failures, another scenario

I am having another ignite failure, it is an N4000 server running 11.11. Here is the error mesg:

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2008-09-05,09:00/archive_cfg -g
/var/opt/ignite/recovery/2008-09-05,09:00/flist -n 2008-09-05,09:00 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
* Writing boot LIF to tape
ERROR: /usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/dev/rmt/0mn bs=2k failed
to write LIF onto tape.
ERROR: Failed to generate LIF on tape.



======= 09/05/08 09:06:28 EDT make_tape_recovery completed unsuccessfully


Also on another L3000 server running 11.00, again ignite is failing with the following error message,

======= 09/01/08 02:04:30 EDT Started /opt/ignite/bin/make_tape_recovery.
(Mon Sep 01 02:04:30 EDT 2008)
@(#)Ignite-UX Revision C.7.1.93
@(#)ignite/net_recovery (opt) $Revision: 10.862 $ $Date: 2006/11/07
22:27:51 $


* Testing for necessary pax patch.
* Recovery Archive Description = Recovery Archive

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

* Number of Archives to Save = 5

* Pax type = tar


** 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: The list_expander command failed. This could be due to a problem with
parsing /etc/fstab or /etc/mnttab file - see messages above.


======= 09/01/08 02:07:03 EDT make_tape_recovery completed unsuccessfully


Can some one give me some guidance in this regard?
5 REPLIES 5
Torsten.
Acclaimed Contributor
Solution

Re: Ignite backup failures, another scenario

The first looks again like a bad tape or tape drive. Test the tape by writing with tar directly or something like this. Clean drive if needed and try another (new) tape.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
TTr
Honored Contributor

Re: Ignite backup failures, another scenario

The N4000 failed immediately as sson as it tried to use the tape. So like Torsten said, check the tape, drive and connectivity from server to tape drive. For the L3000 check and clean out /etc/fstab. Does it have too many enries in it or too many comments? Don't touch mnttab it is a dynamic file. Are there any other errors in it. It looks like you left a lot the session text out. Also try upgrading IgniteUX to a newer version.
OldSchool
Honored Contributor

Re: Ignite backup failures, another scenario

of course, posting the actual commands issued would be useful
Sandeep_Chaudhary
Trusted Contributor

Re: Ignite backup failures, another scenario

For first error: its tape problem


for list_expander error

check for NFS errors,
Sandeep_Chaudhary
Trusted Contributor

Re: Ignite backup failures, another scenario

Try running list_expander command manually.
it should give u file list.

If fail
then check for "vxconfigd". If not running start it.
#ps -fu root|grep vxconfigd

If it is not running:

#vxconfigd