Restore Ignite image to new server help

[Mike Keys]

I've got twp rp2470's. One is a production boax the other a spare. I've put in some larger blank hard drives into the spare box and would like to take the image of the production server and load it onto the spare box. The hardware is exactly the same.

I've tried the boot lan.IP_Address_of_Ignite_Server install
and ge the -7 error.

Both the Ignite server and the new box are on the same subnet. Performing an SEA does not reveal a lan option on the client.

I've added a temp IP in /etc/opt/ignite/instl_boottab and put in the MAC address of the box we wish to Ignite to.

Is this proper or should I boot from CD and then perform an Ignite restore?

Thought this would be easy.

[Andres Stickar · Accepted solution]

The easy way is to boot from a CD and then perform the restore.

In your Ignite Server you have a directory named /var/opt/ignite/clients where is the clients data.
You will have a directory whit the Mac Address from the original server and a soft link to the name of the server.
To perform the restore with other server you will have to move or rename the original directory to the new Mac address name

F.E.


0x0017A477041C is the original MAC
server1 - > 0x0017A477041C

rm server1

mv 0x0017A477041C 0x0017A478054B
ln -s 0x0017A478054B server1

where 0x0017A478054B is the MAC of the new box.

Regards

Andy

[Andrew Rutter]

hi,

it looks like your ignite serever isnt setup as a dhcp/bootp server.

it needs to be a bootp server to give an ip address out to your new server.

doing a search at pdc, should display an active lan ip.

without this it wont work

-7 error means cannot find anything to boot

Andy

[Mike Keys]

O.K. I was able to get to the Ignite server using the CD method. However, problem #2. I am being told that I have no disks to restore to.

The disk (or paths) show up during the boot and when I interrupt boot at the BCH. The only difference is that I Ignited from a system using 73GB drives and am restoring to an identical system with the exception of using larger hard drives (146GB).

Could this be the reason?

[Mike Keys]

Here is the log file from the Ignite restore (found on the Ignite server). From looking at other Ignite questions, it would appear that the cause of this might be the Ignite versions being used. The CD I am booting from (Dec 2006) is using Ignite C.6.10.97 while the Ignite version used to make the client image is at C.7.4.157.

======= 10/22/08 09:36:51 EDT HP-UX Installation Initialization. (Wed Oct 22
09:36:51 EDT 2008)
@(#)Ignite-UX Revision C.6.10.97
@(#)ignite/init (opt) $Revision: 10.526 $ $Date: 2006/06/20 22:26:23 $

* Scanning system for IO devices...
* Querying disk device: 0/0/1/1.15.0 ...
* Querying disk device: 0/0/2/1.15.0 ...
* Setting keyboard language.
* Bringing up Network (lan2)
add net default: gateway 172.17.1.254
* NFS mounting clients directory.
* Using client directory: /var/opt/ignite/clients/0x00306EF409B6
* Checking configuration for consistency...
ERROR: "/var/opt/ignite/clients/0x00306EF409B6/recovery/2008-10-21,13:07/syst
em_cfg", line 422: Illegal character: "i"
ERROR: "/var/opt/ignite/clients/0x00306EF409B6/recovery/2008-10-21,13:07/syst
em_cfg", line 422: syntax error
ERROR: Problems were encountered while parsing config file: "/var/opt/ignite/
clients/0x00306EF409B6/recovery/2008-10-21,13:07/system_cfg".
ERROR: net_cfg_prep: Problems were encountered while parsing the
configuration files. See the messages above for details. Using
instl_adm with the -T and/or -D options on the server may help isolate
the problem. (See instl_adm(1M) and instl_adm(4) man pages.)
ERROR: Cannot initialize I/O data: unable to open IO file:
/var/opt/ignite/clients/0x00306EF409B6/io.info.
WARNING: read_hw_info: Initialization of the IO tree failed.
ERROR: No disks found on system.
NOTE: Cannot access file:
/var/opt/ignite/clients/0x00306EF409B6/config: - ignoring

NOTE: The disk at HW path: 0/0/2/1.15.0 does not exist on the system and was
specified in the configuration for the system. No substitute disk
could be found, so it will be removed from the configuration.
NOTE: The disk at HW path: 0/0/1/1.15.0 does not exist on the system and was
specified in the configuration for the system. No substitute disk
could be found, so it will be removed from the configuration.
NOTE: The volume group vg00 will be removed from the configuration since
there are no disks associated with it.
ERROR: Unable to find any disks on the system. Please check the
hardware, reboot, and restart the installation process.

[Andres Stickar]

You will have not problem to restore the system to a bigger disk.
In fact this is the way to grow up in disk capacity in the vg00.

If you cannot see the disks could be because the Ignite version you are using to boot.
Is a best practice to use the same version to boot and to restore the ignite.

If you are not able to boot from a newer version you must configure the bootp in your ignite server to provide a boot option.

Regards
A.

[Andrew Rutter]

hi,

both ignite versions should be the same or as near as can be.

however, you also have errors with the cfg files as well? it seems.

when you created your recovery archive, i assume you amended the cfg files as required and ran inst_adm -t across them?

if not check them again and look at 422 of the system_cfg file?

Andy