1842011 Members
2839 Online
110185 Solutions
New Discussion

Re: Ignite UX

 
Dario_4
Frequent Advisor

Ignite UX

Hello admins,
i wuold like to know if is possible to use Ignite UX B.3.3.116 because, when i try to read the man page of make_boot_image, i see this:

1. Obtain and install Ignite-UX version B.2.4.307. Other versions may be incompatible and are not supported.

I use HP-UX 11.00.03. Some suggest?

Thanks in advance
9 REPLIES 9
harry d brown jr
Honored Contributor

Re: Ignite UX

Well, its better to use the newer version than a very old version.

Maybe your man pages are old?

live free or die
harry
Live Free or Die
Dario_4
Frequent Advisor

Re: Ignite UX

Ok, thanks a lot.
No, my man page is new.

Sanjay_6
Honored Contributor

Re: Ignite UX

Hi Fabrizio,

Most of the time, it suggests you not to use anything below that version. It cannot suggest something above that version since at the time that doc was prepared the new version was not out yet.

So it is safer to assume, you can use a version equal to or above the version mentioned. There is a possibility if you use a newer version, it may not be correctly read and understood by the older version. But the Vice versa should be okay.

hopr this helps.

Regds
Eileen Millen
Trusted Contributor

Re: Ignite UX

You can get Ignite version 3.3 from
http://www.software.hp.com/products/IUX
There are some patches listed also.

Eileen
Deshpande Prashant
Honored Contributor

Re: Ignite UX

HI
Your Ignite Version B.3.3.116 is not too old.
I have same version on my system and do not see the command make_boot_image or its man page.
Correct me if I'm wrong, you may want to use "make_sys_image" command instead.

Thanks.
Prashant.

Take it as it comes.
Patrick Wallek
Honored Contributor

Re: Ignite UX

I think you may have the man pages from an older version of Ignite/UX. When I upgrade Ignite I ALWAYS swremove the old version before installing the new version. I had problems once when I just installed the new over the top of the old.

I am running 3.3.116 and 3.4.115 on different machines and neither one has the man page for make_boot_image, nor is there a file in /opt/ignite or /var/opt/ignite called make_boot_image.

Dario_4
Frequent Advisor

Re: Ignite UX

Well admins,
apparently it works fine.

root@testmnp [/]
# make_boot_image
Checking size of /stand filesystem.

This will update the flash card in /dev/rflash/c3a0d0.
Please remove the current boot flash card there
and put in a different flash card to use for recovery.
You have time to do this while the flash image is created.
This will take approximately 40 minutes.

Creating flash image. : Approximately 20 minutes.
Copying flash lif to flash image. : Approximately 10 minutes.



One thing:
which is the correct options to use with make_recovery for backup all system?
The man page speak about -Ai (for all boot disk and interactive mode) but this include all files presents in all disks?

Thanks again
James R. Ferguson
Acclaimed Contributor

Re: Ignite UX

Hi:

You really should stop using 'make_recovery' and start using 'make_tape_recovery'. The later is more robust. 'make_recovery' is being phased out.

To create a tape recovery archive of all of vg00, do this:

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

The '-I' option of 'make_tape_recovery' is the *same* as the '-i' option of make_recovery. '-I' means cause the Ignite process to be interactive when booting from tape.

Note that you can *include* and *exclude* files and directories as you like, and as shown, can select whole volume groups.

The directory ' /var/opt/ignite/recovery/latest' contains the 'manifest' file from the process as well as the 'flist' file which lists the contents of the archive.

Regards!

...JRF...
Patrick Wallek
Honored Contributor

Re: Ignite UX

I don't know about the make_boot_image. That is not something I'm familiar with and it is definitely not part of the current version.

Anyway,

If you are using make_recover, use the -Ai optoins. This will back up your entire vg00 volume group, AND if you happen to have /usr in a vg other than vg00, then the VG that contains /usr/ will be put entirely on the tape as well.

Excerpt from make_recovery man page:

"With the -A option specified, all of the root volume group is archived. If /usr is not on the root volume group, then the entire volume
group on which /usr resides is also archived. This is because of core files needed from the /usr directory."

Now, since you have the newer version of Ignite/UX I would use the make_tape_recovery command instead.

The recommended syntax is:

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

This will backup your entire VG00 volume group.
You should use Ignite/UX to back up only vg00 stuff, unless you have a very small system. Its intended use is just to back up VG00 to give you a very easy way to recover the OS in case of a catastrophic system crash. It is assumed, if you have other data in other VGs, that you have some other method to backup and restore that data should it be necessary.