Ignite-backup from Ignite-server

[SGUX]

Hi All,
i want to use one of my HP-UX-servers, with DVD-RW, as an Ignite-server and brun the images on DVD with make_opticaldisc_recovery. But i also would like to get the Ignite-image
of this (Ignite-)server on DVD. Somehow i can't find how to create an Ignite-backup of my Ignite-server. Anyone knows how to do this ?

[AwadheshPandey]

http://docs.hp.com/en/B2355-90153/ch04s03.html

[SGUX]

If have seen the doc, downloaded the latest Ignite-UX Administration Guide but i just can't seem to find what i need in it.

[J. Bravo]

http://docs.hp.com/en/5992-0602/ch11s03.html

[Torsten.]

I did not try this yet, but if I read the manual:

"The make_opticaldisc_recovery script can be used to create a recovery image and then write it to a DVD. The script creates the recovery image with make_net_recovery, and then calls make_media_install to write the recovery image to DVD. This script is to be run from the client system, and requires one argument â the hostname or IP address of the Ignite server. The script first creates a recovery image of the client and stores it on the Ignite server. Then, the recovery image is written to the Ignite server's DVD writer. The make_opticaldisc_recovery script was introduced in Ignite-UX version C.7.2."

http://docs.hp.com/en/5992-0602/ch11s03.html#d0e13040

I understand what it says that way:
1) backup client to server
2) write backup to server's DVD

To backup *your* ignite server you must backup it to another server (or tape).

[SGUX]

This is what i found in the manual as well.
But this also implies that you always need 2 Ignite-servers to backup your complete environment. Guess it is easier (and cheaper) to get a tape-device and run a make_tape_recovery for the Ignite-server.
(i still do not understand why HP did/does not create a make_dvd_recovery for the newer smaller-servers supllied with DVD-RW)

[Aneesh Mohan]

To create an ignite CD image, here are the steps you need to follow:

Step 1: Create the logical Volume. This one takes some tweaking especially if you are having
problems creating an image that will fit on one CD. The size of the file system you create
makes a big differance because later on in the procedure you do a dd of the file system, which
copies byte for byte the entire file system into a file, so if you have a 2 gig file system, it
creates a 2 gig file. so this file system can be no bigger than about 625 Meg due to the fact
that you have to wrap a lif volume around the file system, so it bumps it up closer to 650 meg
when all is said and done. What I did, was I had a 630 Meg file system, I created my system
image, and saw that the final system image was 562 meg in size so I created another file system
that was 580 meg in size so to not leave much extra space and put the gz file in there. If you are
having problems getting the image to fit, trying clearing out log files, /tmp and doing a
cleanup -c 1 on the system to remove any extra stuff that could be taking up alot of space....but
anyways, that is getting ahead of myself a bit....for step one, just create a file system, I will
go with the final numbers for what I used:

lvcreate -L 580 -n image2 vg00
newfs -F hfs -f 2048 /dev/vg00/rimage2
mkdir -p /var/tmp/image2
mount /dev/vg00/image2 /var/tmp/image2
cd /var/tmp/image2
rm -r lost found

Step 2: Access a CD-ROM Archive. Create the image:

/opt/ignite/data/scripts/make_sys_image -d /var/tmp/image2 -s local

This step is the long one, it took about 3 or so hours for it to run when I ran it.
The output from this step is a file in the /var/tmp/image2 dir that is 'hostname'.gz so
in my case, drmsd4.gz

Step 3: The Config File: If you look at the "building an install cd-rom" procedures, it talks
alot about configuring depots n stuff, and I originally tried doing that by adding ignite and ssh
to the image, but when I ran into the size issues, I quickly just gave that part up and only dealt
with the generic image stuff....later, perhaps we can add everything to the depot part, but for
now, I am leaving that part out of this doc. For the config file you DO need, type:

cp /opt/ignite/data/examples/core.cfg /var/tmp/archive.cfg
then you are going to need to modify this file, but before you do that, you are going to need to
get an "impact" list. you get that by typing:

/opt/ignite/lbin/archive_impact -t -g -l 3 /var/tmp/image2/drmsd4.gz

this takes about 20 or so minutes, and outputs to the screen three levels of the file system that
is in the gz file. you need to copy all this stuff and paste it into the archive.cfg file...so go
ahead and copy the output, the vi /var/tmp/archive.cfg.
once in the archive.cfg file, search for source_type="NET" and change the NET to DSK. Then down
a few lines, uncomment the change_media=FALSE line. Then down a few more lines, comment out the
nfs_source = line. Then skip past all the model 700 stuff until you reach the "S800 OS archives"
section. look for a line that starts with "archive_path =". and change what it equals to
drmsd4.gz (the gz file that you created in step 1). Right below the commented out archive_path
line, you will see a list of a few impacts.. Delete them all, then paste in the ones you have in
your clipboard. Once that is done, go ahead and :wq out...

Step 4: Assemble the CD-ROM. Almost done. all you have to do for this step is umount the file
system that has the .gz in it and do a dd (that should be the only thing in that dir, and it should
barely fit in that file system. You also need a place big enough to hold the image, I used the
patches dir. So basically what I typed was:

umount /var/tmp/image2
cd /midtier/patches/source
dd if=/dev/vg00/rimage2 of=./fs_image bs=1024k

Step 5: Create the LIF Volume. I dont really understand what a LIF really is, so I am not gonna
do much jabbering in this step....just type:

make_medialif -f /opt/ignite/data/Rel_B.11.00/config -f /var/tmp/archive.cfg -l ./lifvol

Step 6: Modify INSTALLFS Config. This step took some figuring out for me since the documentation
provided sucks at this point, basically you need to add a few lines to the installfs configuration
that is in the lifvol, you do this by typing in the following:

instl_adm -d -F ./lifvol > ./cfg
vi ./cfg

once in the cfg file, add the lines:
run_ui="TRUE"
control_from_server="FALSE"
save and quit, then type:

instl_adm -f ./cfg -F ./lifvol
The above puts it in.
instl_adm -T -F ./lifvol
The above checks for errors
instl_adm -d -F ./lifvol
The above verifies the changes.

Step 7: Make the image. This is quick and easy, basically, you have to wrap the lif volume around
the fs_image. To do that, just type:

/opt/ignite/lbin/instl_combine -F ./lifvol -C ./fs_image

after about 40 seconds, you have a prompt, and fs_image is ready to go...verify that it is less
than 650 meg, or you will have a problem burning it to a cd ;)

Step 8: Burn to a CD. Ok, bring up the cdwriter software, then change the source location to
imagefile, click on options, and select your fs_image file (you cant just burn the fs_image to
the cd like you would normally, it wont work, an image file gets "un-wrapped" when it is burned to
the disk. once you pick your souce file, make sure the target is pointing to the cdwriter (which
is never is when you first start it up), once that is done, just "write" the disk....after about
15 or 20 minutes, you have your ignite CD ;)

Aneesh

[Torsten.]

I would agree, it could be very comfortable to backup a system to a DVD directly.

Meanwhile consider to take the ignite servers backup to a tape or another ignite server...

[SGUX]

doesn't necesseraly need to. I managed to do a make_net_recovery from the Ignite-server.
[ carefully reading the (errors in) the logfile does make a difference ]
Had to manually create an entry in /etc/exports and permit direct rootlogon via ssh. After this the an archive was created.
So up to the next step, write it to DVD.

Evrybody thanks for the replies.