Possible to use make_net_recovery Archive as Golden Image?

[Alzhy]

I know its possible to make a ignite_recovery tape out of a net_recovery archive, but is it at all possible to for a make_net_recovery archive to be installed as a golden image on an ignite server? I know I've tried this once before.. just copying the archive file and doing archive_impact on it but archive_impact just returns an error... My net_recovery archives are default formatted .. gzip tar.

Am trying to clone an environment to a server that does not have a locally attached tape device.. the target server is actually a vPar.

I was planning in just breaking the mirror off of this reference server (another vPar) and use that disk.. boot in maintenance mode, change the VG.. change networking info, etc... but I thought an Ignition out of a make_sys_image would be better.

The reference server is very busy so I cannot just get a make)sys)image window to get an image off of it -- and make_sys_image renders the server unsuable/unloginable for the duration of the make_sys_image..

Suggestions?

[Robert-Jan Goossens]

Hi Nelson,

Looking for these instructions ?

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

Regards,
Robert-Jan

[Alzhy]

Nope... I already know how to make a bootable Ignite recovery out of a net_recovery archive as well as how to configure a Ignite server to include as one of the installable options a golden image.

My primary inquiry is if it is possible to use a make_net_recovery archive (file) so that I could use at as an Ignite "golden image"... I thought it was just as simple as having this very file as my "image.gz" file but in the steps to configure it into Ignite, once step (archive_impact" .. fails.. It does not seem to recognize the format of the make_net_recovery file which I have spec'd as tar gzip format...

[Michelle Barton]

Did you ever figure this out? I'm trying to do the same thing now.

Thanks,
Michelle

[Scot Bean]

I have not attempted this backup convert to golden image.

However, in general, golden images need filesystem "impacts" statements in the "sw_sel" portion of the configuration file.

These impacts are predetermined by running the /opt/ignite/lbin/archive_impact cmd against the .gz file.

[jmazzaro]

archive_impact requires two options:
-g if you have a gzipped archive
-t | -c depending on tar and cpio.
I actually am getting an output, the impact statements are wrong. For example, even though my /home directory is a measly 200MB in size, my archive impact statement for home is:
impacts = "/home" 247192338Kb

This is strange