URGENT: make_net_recovery change filesystem sizes on restore

[Craig A. Sharp]

I need to restore a server from an ignite server on a different subnet. Also I need to be able to change the file system sizes on restore.
Nother issue is that I need to use a different lan from the on that was used to create the make_net_recovery.

Can anyone provide instructions on how to make this happen?

[DCE]

Refer to the boot helper section of the manual (see attached link) for instructions to boot from a different segment.

http://docs.hp.com/en/B2355-90970/index.html


Do the interactive Ignite restore to be able to change logical volume/file system sizes. The menu will walk you through the changes.

[Steven E. Protter]

Shalom,

After you have successfully booted your ignite client off the server (boot helper above), you will then need to watch the screen at the console.

You will see a prompt that lets you press any key to do an interactive install.

Within the limits of available disk space, you can change filesystem size.

This is the method many sysadmins use when a system has a filesystem that can not be expanded that is now too small.

SEP

[Craig A. Sharp]

cool...thanks for the replies...I am trying to figure out how to boot from one of the lan paths..my path is

1/0/2/1/0/6/0

I have tried:

bo 1/0/2/1/0/6/0.172.x.x.x install

No luck...

Any ideas?

[IT_2007]

search for Ignite Servers like this:

search lan install

and do you see Ignite server IP address?

[Craig A. Sharp]

No, I have a feeling I need a boot helper.

[IT_2007]

Also you need to link config files to new LAN address.. look at man page for make_net_recovery.. it says like :

make_net_recovery(1M) make_net_recovery(1M)

+ If the client system is being replaced, or the LAN card has
changed since make_net_recovery was last used, you should
manually rename the old client directory prior to starting the
recovery. Not doing so will cause a new directory to be
created and you will not see the recovery archives created
under the old client directory. To rename the client
directory, obtain the new LLA address (you may use the
LanAddress boot-ROM command in the information menu), then use
the mv command. For example:
cd /var/opt/ignite/clients
mv 0x00108305463A 0x0060B0C43AB7
If you have already booted the new system, you will need to
remove the new client before renaming the old directory. Be
careful not to remove the old directory containing the
recovery information.

[IT_2007]

you can do push / pull method.

If you use boot helper then it would be easier to restore using pull method. Still you need to link new LAN MAC address to the image on Ignite server. You can get this LAN information when you see Ignite gui on client.

[Bill Hassell]

Booting from an Ignite network server requires that the server be on the same wire (subnet) because the ROM bootup code knows nothing about routers and subnet masks. Also, you can generally only boot from the built-in LAN, not add on LAN cards. The boot-helper must be on the same subnet and provides a small kernel that knows about networking, at which point the rest of the recovery can be over router(s).

[Tom Danzig]

It may be easier to create a boot tape on the Ignite server and boot from that. Just insert a tape and run /opt/ignite/bin/make_boot_tape -d and boot the client off that. I find it easier than setting up a boot helper.

Also, you can only boot from the built-in NIC as well which can cause network boot issues as well. Food for thought.