Ignite-UX
cancel
Showing results for 
Search instead for 
Did you mean: 

make_tape_recovery showing some error

 
SOLVED
Go to solution
ani007
Super Advisor

make_tape_recovery showing some error

HI,
I am trying to take ignite backup on tape.
OS 11.11. model 9000/800/rp4440 .But i am getting some error
=========================
ERROR: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg", line 772:
Illegal character: "t"
ERROR: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg", line 772:
syntax error
ERROR: Problems were encountered while parsing config file:
"/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg".
instl_adm: Config file: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg" cannot be parsed.
ERROR: /opt/ignite/bin/instl_adm failed checking syntax for
/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg
ERROR: Failure checking syntax of
/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg
ERROR: /opt/ignite/bin/instl_adm failed checking syntax for
/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg
ERROR: Failure checking syntax of
/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg
NOTE: File: /var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg is not
world-readable, this may cause clients to fail to read it during an
installation.
ERROR: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg", line 772:
Illegal character: "t"
ERROR: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg", line 772:
syntax error
ERROR: Problems were encountered while parsing config file:
"/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg".
instl_adm: Config file: "/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg" cannot be parsed.
ERROR: Failure creating the archive configuration
ERROR: make_arch_config failed.
====================================

I have deleted the line in the file

"/var/opt/ignite/recovery/2011-03-14,11:51/archive_cfg" - still again when i am fire "/opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn I -v -x inc_entire=vg00" i am getting same error again & again...
could you please help

Regards,
Ani
10 REPLIES 10
Steven E. Protter
Exalted Contributor

Re: make_tape_recovery showing some error

Shalom Ani,

Please post:

swlist -l bundle | grep -i ignite

These configuration files are created as part of the backup to facilitate restore of the data.

After the delete you will need to re-start the backup.

You need a certain amount of space free in /var

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
ani007
Super Advisor

Re: make_tape_recovery showing some error

Hi tnx for your reply. I fired the below command now it is going on

make_tape_recovery -a /dev/rmt/0mn -A -x inc_entire=vg00

I have not seen any error still now ....

but for other server facing some strange issue while i am taking this ignite..
======================
WARNING: The /dev/null file is not a character device file.
WARNING: The /dev/null file is not a character device file.
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2011-03-14,13:32/system_cfg
ERROR: A problem has been detected in determining which volume groups and/or
disks are to be part of the recovery archive. This could be due to a
failure of the "list_expander" command. Ensure that the
"/opt/ignite/lbin/list_expander" command returns valid output and
retry.

======= 03/14/11 13:32:44 EDT make_tape_recovery completed unsuccessfully
xxx):/root/home/root (root)
====================================
the above server o/p is

xxx):/root/home/root (root) swlist -l bundle | grep -i ignite
B5725AA C.6.2.241 HP-UX Installation Utilities (Ignite-UX)
xxx):/root/home/root (root)
Highlighted
Alex Glennie
Honored Contributor

Re: make_tape_recovery showing some error

vgdisplay -v ?

/opt/ignite/lbin/list_expander ?

ll /dev/null

would help a lot ....



ani007
Super Advisor

Re: make_tape_recovery showing some error

hi please find the attachment
Alex Glennie
Honored Contributor

Re: make_tape_recovery showing some error

Thanks and do you see anyhting special about the character device file, perhaps try changing it and re-running ignite and/ or list expander

eg http://h30499.www3.hp.com/t5/Ignite-UX/list-expander-command-failed/m-p/5163723#M22163

ani007
Super Advisor

Re: make_tape_recovery showing some error

Hi Alex,
Tnx for your quick reply.


ignit_02(OVO8):/dev (root) ll null
-rw-rw-rw- 1 root sys 0 Mar 14 15:18 null
ignit_02(OVO8):/dev (root)

1. rm /dev/null

now how i will create it again? from that thread #mknod c 32 /dev/null is not working

ignit_02(OVO8):/dev (root) mknod c 32 null
mknod: arg count
usage: mknod name b|c major minor
mknod name p
ignit_02(OVO8):/dev (root) mknod c 32 /dev/null
mknod: arg count
usage: mknod name b|c major minor
mknod name p
ignit_02(OVO8):/dev (root)
ani007
Super Advisor

Re: make_tape_recovery showing some error

can i copy it from other server????/ will it create any problem if i copy it from any other 11.11 box? this is our production server..
Bill Hassell
Honored Contributor

Re: make_tape_recovery showing some error

See the answer in another thread. /dev/null is used by a *LOT* of programs and scripts and a file cannot be removed until all programs no longer have this file open. You can't copy /dev/null from another server -- it is not a regular file. list_expander found this error for you. You'll have to reboot into single user mode to remove the regular file and run the mknod command. As root, NEVER remove /dev/null once it has been correctly created.


Bill Hassell, sysadmin
Dennis Handly
Acclaimed Contributor
Solution

Re: make_tape_recovery showing some error

>mknod c 32 /dev/null is not working

The other thread had: c 3 2

>Bill: a file cannot be removed until all programs no longer have this file open.

No, a file can be removed from the directory entry at any time. But you have to weigh the consequences.

>You'll have to reboot into single user mode to remove the regular file and run the mknod command.

I'm not sure why?
Just mknod /dev/null2 and then move old and new in place:
cd /dev
mv null null.bad; mv null2 null

Hopefully the window is small enough.