12-08-2005 05:00 AM
I've looked at the steps for make_tape_recovery in Patrick Walleks document but there seems to be a few differences between a tape and net ignite image.
Such as more config files. And, for example, I can't determine which cfg files to use for the make_medialif.
Here's some background information on my situation.:
This is how I create the ignite image:
-------- Start of script ---------
export HOST=`uname -n`
$IGPATH/make_net_recovery -s [IP of ignite server] -a 10.1.x.xxx:/images/$HOST -A -b -d "$HOST for $IGNITEDT" -n 3 -m tar >/tmp/ignitelog.log
if [ "$?" -eq 0 ]
cat /tmp/ignitelog.log | mailx -s "Ignite of $HOST was Successfully Completed" email@example.com
cat /tmp/ignitelog.log | mailx -s "Ignite of $HOST FAILED" firstname.lastname@example.org
-------- end of script ---------
This creates files in two locations:
Config files are in:
The actual image is in:
Solved! Go to Solution.
12-08-2005 05:53 AM
You can create a bootable DVD from your system using the exact same tools as make_net_recovery.
Here is a document.
All you need to do is change the make_sys_image parameters to create the image you wish.
The procedure above works with HP-9000/Integrity DVD writers. They seem to only like DVD RW+ media.
Owner of ISN Corporation
12-08-2005 07:24 AM
On a weekly basis I run make_net_recovery on all my systems.
This creates an image on my Ignite server in /images/servername/imagename
Could I not skip the make_sys_image step and use the image created by make_net_recovery with some cfg changes?
Or is there something fundamentally different in the two image types?
12-08-2005 10:39 AM
make_sys_image is the only command to create the ignite image. Even the make_net_recovery internally calls the make_sys_image for creating the images.
Instead of using make_net_recovery , u can use mak_sys_image itself to copy the image in another server.
#make_sys_image -s (servername) -d (dest directory) -n (archieve name).
12-08-2005 10:55 AM
The below link refers the admin guide, Please see the 8th chapter and creating DVD media.
As I told you, instead of using make_net_recovery, use make_sys_image itself to create image on remote m/c, where DVD RW+ is avial. And create the DVD.
01-04-2006 07:23 AM
But just an FYI
This is why I want to use the image from make_net_recovery.
We have an existing automated process which creates ignite images of all our HP-UX servers to our Ignite server. Using make_net_recovery.
So instead of re-running the image create process on our extremely busy systems I want to be able to use these existing images to create the bootable DVD.
If anyone has done this please let me know how.
01-10-2006 08:25 AM
The problem is that make_sys_image seems to want to archive the ENTIRE /dev/vg00.
Whereas I only want the minimal OS required. And will possibly add a few customization later once I know I can create a bootable DVD.
How can I stop make_sys_image from archiving the entire vg00 and just do what's required for a minimal OS?
01-11-2006 08:30 PM
You can edit the
make_sys_image script and
edit the LEVEL2_NO_ARCHIVE protion of the file to include the files/directories that you want to exclude from taking bakup / in the image.
01-12-2006 03:55 AM
I am editing the LEVEL2_NO_ARCHIVE portion of the file to include the files/directories that I want to exclude from the image.
But I'm trying to recall where I once saw a configuration file which defined the minimal core OS files for an image.
I want to use that as a starting point to verify I have everything I need for a valid archive.
Valid meaning I don't want to exclude files required for the OS to operate properly.
04-17-2008 04:15 AM
They finally invested in the hardware at the DR site!!! yay!