Golden Image of 11.11 system

[J.D._3]

I have created an archive image of an A Class system running HP-UX B.11.11 on a directory /iux_images/sys1. This system does not have a tape drive but I also wanted to keep a backup to tape using another machine. I went through some search and found that I still have to create a LIF file in order for this tape I want to create to be usable for igniting other systems. The problem I have is non of the examples in the make_medialif man pages are for an 11.11 system. Would these examples work for me? The other reason I would like to put it on tape is to verify the contents of the archive. Is that the only way to verify the archive of an image? Thanks in advance.

[Patrick Wallek · Accepted solution]

The examples in the man page *should* be release independent. Another good document on how to create a tape from a network archive is /opt/ignite/share/doc/makenetrec.txt and look for the section on creating a tape.

You can verify a make_net_recovery archive, at least the pax backup portion, by going:

# gzcat | tar -tvf -

That will list all of the files on the screen for you. If you want the file list in a text file to view later:

# gzcat | tar -tvf - > /tmp/somefile

[Steven E. Protter]

The A class should do make_tape_recovery to an Ignite Server.

That will create an archive file.

Back that up along with the configuration of the Ignite Server itself and you've got it on two tapes.

The only way I trust to verify an image is to restore from it.

SEP

[J.D._3]

Patrick,

Thanks for the reply. I went through that file as well, and that's how I realized that I have to create a lif file. It talked about 3 cfg files (system, control, and archive). Where do I get these? I guess I needed more understanding on what these cfg files consists of. I used the core.cfg file in /opt/ignite/data/examples to create the lif below: Would this work?

# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="127.0.0.1"
netmask[]="255.255.255.0"
route_gateway[0]="172.31.50.254"
route_destination[0]="default"
run_ui=false
control_from_server=false
env_vars += "INST_ALLOW_WARNNGS=10"
env_vars += "INST_BATCH_MODE_TIMEOUT=10"
# end instl_adm defaults.


Steven,

We will be using the A class as the ignite server and will be storing the images on a emc storage array. As of now the image is local because we haven't put the necessary cards to hook it up to the san switch and the A class hasn't a tape drive on it. But yes, if I had a drive, I could definitly use a process like this.

[Steven E. Protter]

Good show.

You'll need to customize your make_sys_image file and your Ignite profiles.

What you'll also want to do once the Ignite system is deployed is regular make_net_recovery jobs on the Ignite clients. The Ignite Server will act like a little DR center onsite. An Ignite tape of the A-Class plus a backup of the make_net_recovery archives could put you back in business at a DR site within hours.

We are in the process of doing just this right now, though we are further along.

Makes sure that A Class has a large disk area dedicated to ignite golden image and archive files so you can do the job right.

SEP