Ignite Tips

[Xavier Gutierrez]

Hi, guys.

I'm doing a compilation of Ignite UX tips.
So, if you want to post some of them on this thread...

PS: I will take care of cut & pastes so, please be original...

[harry d brown jr]

Veritas's bare metal restore is not a replacement for IgniteUx, but a blank piece of paper is a replacement for veritas's bare metal restore!

live free or die
harry

[Clemens van Everdingen]

Hi,

I agree and also read these pages:

http://www.software.hp.com/products/IUX/faq.html

http://www.software.hp.com/products/IUX/

And keep yourself up to date with the latest versions.

C.

[Bill McNAMARA_1]

use make_bundles to create a patch bundle, include the patch bundle config in the Index file for each archive.. one of the easiest ways to "update" the archive/golden image..

I recommend using the Ignite gui as error messages are often more readable than the cli and in cases where permissions are causing problems, it'll ask you to correct rather than abort.

The ignite FAQ and Admin guide found on software.hp.com is worth a look!!

Later,
Bill

[Pete Randall]

I've got one tip: Use it - and use it regularly.

Pete

[Patrick Wallek]

To restore a single file from an Ignite/UX tape (make_tape_recovery):

# mt -f /dev/rmt/?mn rew
# mt -f /dev/rmt/?mn fsf 1
# tar -xvf /dev/rmt/?mn dir/filename

NOTE: That there is NOT a leading / or ./ on the path of the file you are restoreing.


To restore a single file from an Ignite/UX Network archive (make_net_recovery):

# gzcat network_recovery_archive_name | tar -xvf - dir/filename

Use make_tape_recovery or make_net_recovery on a regular basis. We have most of our machines doing a weekly make_tape_recovery.

[James R. Ferguson]

Hi:

In lieu of using 'tar' to extract file(s) from an Ingite 'make_recovery_tape' [documented in that command's man pages], use 'pax'. You can easily extract files to your current working directory. See the 'pax' man pages for more information.

Regards!

...JRF...

[John Dvorchak]

To determine when an Ignite tape was created I use:

1. mt rew
2. dd if=/dev/rmt/xm of=/tmp/tapelif bs=2048 count=10
3. lifls -l /tmp/tapelif
4. the date is listed yy/mm/dd

Here is a sample output.

volume ISL10 data size 281239 directory size 3 02/11/27 18:02:16
filename type start size implement created
===============================================================
ISL -12800 16 240 0 02/11/27 18:02:16
AUTO -12289 256 1 0 02/11/27 18:02:16
INDEX BIN 264 1 0 02/11/27 18:02:16
CONFIG BIN 272 37 0 02/11/27 18:02:17
HPUX -12928 312 880 0 02/11/27 18:02:17
INSTALL -12290 1192 26990 0 02/11/27 18:02:25
INSTALLFS -12290 28184 31744 0 02/11/27 18:02:33
FWWKAR BIN 59928 1 0 02/11/27 18:02:33
INSTCMDS BIN 59936 10750 0 02/11/27 18:02:35
SYSCMDS BIN 70688 45488 0 02/11/27 18:02:44
SCRIPTS BIN 116176 42 0 02/11/27 18:02:44

[Wodisch]

how about:
- using "-I" (interfactive restore) on "make_*_recovery"
- using "VG" parameters with bigger PE-sizes
- using "Golden Images" instead of "cold installs"

FWIW,
Wodisch

[John Poff]

Hi,

I have a tip. Keep your vg00 clean and free of any extra filesystems that really belong in another volume group. We had a production system where somebody created a 2Gb filesystem in vg00 to store Oracle patches. It sure slowed down the creation of Ignite tapes, not to mention the joy of sitting through an extra 2Gb of data spinning off of a DDS tape when we were trying to recover a system!

JP

[SSO Montgomery]

JP, keep a clean vg00 tip is worth AT LEAST 25 points! Great advise.

[Tom Jackson]

Hi:

Keep the most recent ignite tape offsite for contingency planning.

I use the following command to backup my entire root volume, including /opt:

make_recovery -A -C -v -d /dev/rmt/0mn

Tom

[Dean_51]

Information passed to Xavier...post edited for privacy by moderator.