Using ignite to clone servers where hw differs

[OPM Marienborg]

I want to clone two servers, one RP3440 and one RP5170. I've made a ignite-tape on the RP3440 and booted on the tape on the RP5170. The tape starts , but errors short after (see attached file). My question is itpossible to do this in this way or must the hw configuration be equal on both servers?

[Pete Randall]

Not necessarily equal but at least similar. It would be helpful if HP had some sort of compatibility chart but I'm unaware of such a thing.

To ensure your best chance of this succeeding you should install the latest HWE bundles before on the rp3440 before creating your Ignite tape.


Pete

[Pete Randall]

Looking at the specific errors in your attachement, it would seem that at least part of the problem could be cleared up by either running interactively or figuring out where you can specify "allow_disk_remap=true".

The other error that concerns me is the first one:

"There is no root volume (mount point = /) defined in the configuration."

I'm unsure whether an interactive restore would be able to correct that or not, but it should be worth a try.


Pete

[F Verschuren]

the error looks lik e it can not find the disk to install on this can meen some thing:

1 wrong disk is giving to restore the ignite on
2 the disk is not asseble due to a lek of drivers.
3 the HW path of the console is set wrong
4 hartware problems

[Victor BERRIDGE]

Well
I understand 2 things as a biologist (my previous life) cloning is an exact replica to be made, I dont see how it can be done if the 2 boxes are not exactly the same...
Now if its only software (OS etc...) then Ignite may very well work but of coures will complain because not finding the same hardware to configure...
This is only a matter of giving the good hardware paths and adequately redimentionning the file systems to suit the new disks, and of course NOT giving the IP (unless it is not connected to the lan...) etc..
It may need some extra drivers but that could be completed with CDs...after basic installation has completed...


All the best
Victor

[OPM Marienborg]

Okey, I've settled to just install from CD. As replied, this isn't really a clone since the hostname/IP etc isnt the same.

Is there a way to copy a patchset from one system to the other?

[paolo barila]

Hi,
I was able to restore a ignite tape from a L3000 to a N4000, I had your same warning, but no error and it worked.
I think specifing -i option could help.

[Victor BERRIDGE]

Yes and I used a K360 tape to install a D280,a e35 tape for a D210...

Good luck
Victor

[Victor BERRIDGE]

And thinking of it,
I wonder since the rp3440 is more recent than the rp5470 if it is nit some firmware revision trouble... upgrade the firmware first!


All the best
Victor

[OPM Marienborg]

How do I specify the -i option? In the ISL?
or at creation of the ignite?

[Victor BERRIDGE]

Since you have a tape, dont bother to make a new one and look what you have on it:
When the system boot on the tape you will have a short delay to interrupt the process going batch and entering in interactive mode

[Victor BERRIDGE]

It should ask you to press return to interrupt batch mode

Then it should display something like "Welcome to Ignite-UX"


Good luck

[paolo barila]

I use to do "-i" at creation of the ignite

[OPM Marienborg]

Hmm. I'll try once more. My terminal has some problems viewing the menus... Have to find a solution for this first.

[paolo barila]

type Ctrl^L

[Pratyush Paul_1]

hi -

Yes you could do that with a -i option when you do you make_recovery, what it basically doing is creating a ignite tape with an interactive option, when it boots on RP5170 it would clone the device tree etc, this is where ignite comes in handy. The hardware path and device names does not match the old system, hence your process is failing with painic.

Hope this helps.

Thanks

Pratyush

[OPM Marienborg]

I finally got the thing thru. About half an hour ago I started my cloned server with diffrent ip/hw than my donor. The interactive option was the way to go.

My problem with the terminal made the interactive option hidden in some bogus ANSI-coding when directly connected to the console. Tried to use HyperTerminal/Minicom, but no luck. Solved by using a Putty session to the network console port.
Thanks to everyone...