- Integrated Systems
- About Us
- Integrated Systems
- About Us
02-20-2001 08:29 AM
I have just installed a brand new ignite server revision 3.2.
I have 4 new B2000's which I would like to install quite quickly. I thought I could install and configure one of them (this worked), then create a recovery image of it using the Ignite GUI (this worked also) and the restore the image to the other B2000's (this fails).
Apparently there is a check for the MAC-address so that I can only restore the image to that machine.
Is what I am trying wrong ? I know there would be IP-conflicts if I used the exact same settings, but I can change that when I am using Ignite so why can't I even select that recovery image ?
Should I change a configfile or should I use the golden image approach, meaning I have to create one using make_sys_image and than do a lot of textfile editing before being able to put the image on others...
Solved! Go to Solution.
02-20-2001 09:58 AMSolution
(available via autoreply, email to email@example.com with any subject or body content.)
Q: How can I clone a system using make_net_recovery?
A: The recovery configurations and archives created by
make_net_recovery are stored in a separate directory on the
Ignite-UX server for each client.
Using the configuration and archive created by make_net_recovery
on one system to install a different system involves manually
copying some configuration files, and allowing NFS access to
the source system's archive.
The steps to clone a system using make_net_recovery are:
1) Use make_net_recovery (or the "ignite" GUI) to create
a system recovery archive of the source system.
2) Login to the Ignite-UX server.
3) If the target system to be installed does not currently
have a directory in /var/opt/ignite/clients but is up and
running, then use the "ignite" GUI to create that directory
using the "Add New Client for Recovery" action. If the
system is not running, you will either need to boot the
client from the Ignite-UX server (or for a tape made
with make_boot_tape) in order for this directory to
4) Copy the CINDEX and recovery directory from the source
client to the target client directory. Note that if the
target client has previously used make_net_recovery then it
will already have a CINDEX file. If the CINDEX file for
the target system exists already, you may want to save a
copy, and/or hand edit the file to add the desired entries
from the source client. The commands below will copy the
required files, you may specify
(e.g. 0x0060B04AAB30), or by using the client's hostname
(which is a symlink to the LAN address).
# cd /var/opt/ignite/clients/
# find CINDEX recovery | cpio -pdvma ../
5) Give the target-client NFS access to the archive of the
source system. To do this, login to the server that holds
the archive (normally the Ignite-UX server).
Typically each client has its own directory for storing
the archives, and the directory is exported only to the
individual client. In this case, you will need to edit
the /etc/exports file to allow access to both the source
and target clients:
# vi /etc/exports
(append ":target-client" to the end of the
# exportfs -av
6) Now you can boot the target-client from the Ignite-UX
server (using any method you wish). Then when you install
the system, you can select from the recovery configurations
of the source system.
07-20-2005 07:41 AM
Re: golden image or make_net_recovery ?