ignite format

[khilari]

Hi people, just want to confirm. If i have more than one volume groups. Then is this the format i will use for the tape recovery.

make_tape_recovery -x inc_entire=vg00 inc_entire=bg01 inc_entire=vg02 -i /dev/rmt/0mn -l

Kindly confirm, thanks.

[Robert-Jan Goossens]

make_tape_recovery -x inc_entire=vg00 -x inc_entire=bg01 -x inc_entire=vg02 -i /dev/rmt/0mn -l

Regards,
Robert-Jan

[MarkSyder]

Ignite is only for the operating system. Unless you have OS stuff on vg01 and vg02 you should use a different product (e.g. fbackup or Data Protector) for them.

Mark Syder (like the drink but spelt different)

[Patrick Wallek]

Not completely correct. To set the tape drive you actually use '-a' and if you want the tape to boot up into an interactive install you need to use a '-I'. The command should be:

make_tape_recovery -x inc_entire=vg00 inc_entire=bg01 inc_entire=vg02 -a /dev/rmt/0mn -I

That being said, I would advise AGAINST using Ignite to back up anything except VG00. If you need to restore your VG00, then you don't want to have to take the time to restore everything else as well. Also, if just your VG00 is gone, then you really should NOT need to restore everything else, and probably don't want to.

I advise using Ignite for VG00 only, and then using fbackup to backup your other VG's / filesystems.

[Chan 007]

yes

one small change you typed bg01..check that will be vg01.

I guess that is typo

Chan

[James R. Ferguson · Accepted solution]

Hi Khilari:

No, the syntax is wrong. You would specify:

... -x inc_entire=vg00 -x inc_entire=bg01 -x inc_entire=vg02 ...

That said, *however*, I would point out that Ignite is a tool for creating a recovery image of vg00 (or perhaps more properly, a recoverable operating system image). Including non-vg00 filesystems is unwise in my opinion.

You want to be able to recover or clone the operating system configuration. After that, you should restore non-vg00 (application) data from other backups and/or 'vgimport' volume groups. This provides the most rapid, cleanest options for a variety of cloning and recovery scenarios.

Regards!

...JRF...

[Patrick Wallek]

Good catch JRF. I missed the lack of the additional '-x' options.

So it really should be:

make_tape_recovery -x inc_entire=vg00 -x inc_entire=bg01 -x inc_entire=vg02 -a /dev/rmt/0mn -I

[khilari]

Hi guys, well it went fine.Except that when i type
make_tape_recovery -x inc_entire=vg00 -a /dev/rmt/0mn -l // it says that -l option for an interactive recovery should have an option with it.
Now, what that option can be........

[Patrick Wallek]

Did you use an upper case (capitl) 'I' or a lower case 'i'? It makes a BIG difference. The capital 'I' option does not require an parameters. The lower case 'i' does not allow the use of the '-x' options.

Have a look at 'man make_tape_recovery' for the differences.

I recommend to always use '-I'.

[khilari]

After one hour of issuing the command i get this error. And the whole exercise goes unsuccessful.

(mailrtr)root# make_tape_recovery -x inc_entire=vg00 -a /dev/rmt/0mn
* Creating local directories for configuration files and archive.

======= 05/18/06 11:59:23 EDT Started make_tape_recovery. (Thu May 18
11:59:23 EDT 2006)
@(#) Ignite-UX Revision B.4.4.29
@(#) net_recovery (opt) $Revision: 10.611 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2006-05-18,11:59/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
f
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/bin/make_arch_config -c
/var/opt/ignite/recovery/2006-05-18,11:59/archive_cfg -g
/var/opt/ignite/recovery/2006-05-18,11:59/flist -n 2006-05-18,11:59 -r
32 -d Recovery\ Archive -t -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
Adding /opt/ignite/Version file to LIF.
46059+1 records in
46059+1 records out
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2006-05-18,11:59 -m t -w
/var/opt/ignite/recovery/2006-05-18,11:59/recovery.log -u -R -g
/var/opt/ignite/recovery/2006-05-18,11:59/flist -a 3445270

* Preparing to create a system archive

* Archiving contents of mailrtr via tar image to local device/dev/rmt/0mn
.
pax: var/spool/cron/tmp/croutCAIa01056 : No such file or directory
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log
/var/spool/mqueue/xfMAA25105
/var/spool/mqueue/qfMAA25105
/var/spool/mqueue/qfLAA24185
/var/spool/mqueue/xfLAA24185
/var/spool/mqueue/dfLAA24185
/var/spool/mqueue/qfMAA25084
/var/spool/mqueue/xfMAA25084
/var/spool/mqueue/dfMAA25084
/var/spool/mqueue/dfMAA25105

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.

======= 05/18/06 12:53:00 EDT make_tape_recovery completed unsuccessfully


Even if some files were unable to be backed up, why didnt it backup what i had and complete the ignite process???

Thanks