Ignite

[Ali Sunderji]

I am trying to use IGNITE a critical server
and put the image onto the network ( as opposed to a tape). eventually want to set this up in a cron to be executed once a month.

The server I am "imaging" is an rp2470 18GB HD.

Is this a good idea ? and any assistance in the commands I need to use will be appreciated.
THX

[Sajid_1]

This may be a good start:

# man make_net_recovery

[Sridhar Bhaskarla]

Hi,

Recovering a network image means booting from the network which is possible only with having a ignite server.

An ignite server can be setup very easily. Look at the URL

http://docs.hp.com/hpux/onlinedocs/B2355-90750/B2355-90750.html

You can also create a bootable tape from make_net_recovery image.

If I were you, I would not build an ignite server to manage one system.

If you think the above is cumbersome, you can go with make_tape_recovery option. It is simple and proven mechanism for OS recoveries.

-Sri

[John Dvorchak]

I don't necessarily agree that it is not worth the trouble to build an Ignite server for only one system. I think that the ease of building the server and certainly, the no cost option is atractive. Also the backup and restore times are much faster over the lan that with a tape. I would periodically make a tape with make_tape_recovery just to cover my butt. As far as answering your question about a "good idea", I think it is a most excellent idea.

To start the process, make sure that you have the newest version of Ignite on both machines. Then start ignite on the the "server". It works and looks best if done from a GUI environment like CDE. Just type ignite from the command line in a term screen and it will virtually walk you through the process of bringing up an Ignite server. The online tutorial should be engough to get you going but a previous answer here, has the url for some extra docs that you should look at. On the client side, once the server is setup, you can issue the "make_net_recovery" command:

/opt/ignite/bin/make_net_recovery -s server -A

And that is literally all there is to it. You will want to man make_net_recovery to get all of the options that you require. Or just take the defaults of storing two verions of the backup etc.

[Leif Halvarsson_2]

Hi
I think using a Ingnite server is a very good idea. I have used this for several years and can strongly recommend this. The Ignite server yo can use not only for system backup/recovery but also for OS installations, patches, software etc. I dont think you need to set up this in cron if you plan to do this once a month. Use the graphical interface, this is very easy to use and run manualy.

[Tim D Fulford]

IF you are doing this for DR purposes the server MUST be in a different building, preferably as far as way as possible.

I prefere tape not because it is better, or quicker but because it is easily transported (make_tape_recovery). That said creating an Ignite-UX image of a server using make_net_recovery is a great way of cloning systems.

Regards

Tim

[Martin Johnson]

make_tape_recovery tapes can be vaulted off site for DR purposes. You should also have a plan to test these tapes every so often to validate your DR procedures and the viability of the tapes. We do DR testing every 6 months.

HTH
Marty

[Tom Danzig]

I think supplementing recovery tapes with network recovery archives is worth it. I like knowing I have several source for restore should one prove to be NG.

man on make_net_recovery will cover just about everything you need to know. Also, check out /opt/ignite/share/doc/makenetrec.txt for other useful info.

I do net_recovery creation for all servers every two weeks on staggered days and sleep better knowing it's done.

[Kelli Ward]

Hi,

I have built an ignite server and am in the process of backing up critical systems to it via make_net_recovery.

A couple of tips.
Download the latest "Ignite-UX Administration Guide" from docs.hp.com and ignite program from software.hp.com

When you back up a system it will make a compressed (50% approx)archive defaulted in the /var/opt/ignite/archives directory be sure to have a least half of the total file system space for vg00 free(if you choose to include all of vg00, it will not back up any other vg's to my knowledge, they will need to be archived with another program, ie:tar, fbackup)in that directory.

If your (vg00) filesystem fills and entire 18Gb drive, your /var directory's lvol will need 9Gb or more of free space, the ignite* command will tell you how much before creating the archive. (Or you could mount a large drive to /var/opt/ignite/archives.)

The easiest way to start your project will be if your ignite server runs CDE then run the /opt/ignite/bin/ignite *(see man ignite) command which will give you a SAM-like GUI window with a nice little GUI tutorial. (This is no substitute for the Admin Guide but is helpful.)
If not, then export a DISPLAY of what ever system you run with CDE and launching the GUI from that system.
You can use this command to setup clients and perform tape and net backups.

On the Admin guide, pay special attention to Ch. 2 (Installing and Administering and Ignite-UX server), Ch. 4 (Running Ignite), Ch.5 (Installing Clients with Ignite-UX) and Ch.7 (Using Golden System Images)

When you 've successfully built an archive, I highly recommend going over the logs and perusing the files generated by ignite so you can get an understanding of what ignite does.
Also, don't make my mistake of running ignite on a client with less than 64Mb. Ignite requires at least 64Mb on both server and client to operate correctly. My first test client was a little toy 712 system with 32Mb of RAM. The server archived the system just fine but the system crashed with a panic:init page break when I attempted a test recovery.
It worked great when I added 32Mb more of RAM.
(this is in the manual, but I didn't see "client", oops.)

Over all I am very pleased with Ignite as both a net based and tape based archiving program.

Best of luck, Enjoy.
Kel

[Kelli Ward]

Hi,
Small addition to my reply.
I shorted the archive directory.
The default archive directory is:
/var/opt/ignite/recovery/archives
Each archive will be placed in it's own directory with the system's hostname.

For example:
/var/opt/ignite/recovery/archives/Mickey/2002-08-14,09:30

Mickey is a directory named after the system's hostname. 2002-08-14,09:30 is the actual archive file formatted by the date and time is was created.

N/A for this please.

Good luck,
Kel