Ignite Ux from 64Bit to 32 bit?

[Michael_238]

Can I make_recovery_tape on a rp7410 and then restore to a 32 bit k370 using that tape? I was led to believe that this could be done. When I try it, I am unable to properly rebuild the kernel using mk_kernel at the ignite shell. Doesn't make sense to me that you can recover a system with a 64 compiled kernel to a 32 bit system architecture. But that is why I came t here to ask!
TIA

Michael

[A. Clay Stephenson]

First of all, a K370 uses a PA8200 so it is a 64-bit box. It can run either 32-bit or 64-bit HP-UX. The problem is that these beasts are just too different for Ignite to work.

[Steven E. Protter]

Answer: Probably.

Ignite is specifically designed to allow you to move configurations around.

I think the real possible obstacle is the 64 bit to 32 bit issue.

How if your rp7410 was an Ignite server and had a swcopy of the core os on it, I'd say, yes for certain you could do that.

I just did a 64 bit to 64 bit recovery in HP's performance Center on Monday. The hardware was very different but the source media was make_tape_recovery.

There were a couple of extra boots as hardware differences were compensated for.

In the end, I would try this:

make_tape_recovry the K370.

Try it.

See what happens.

If it does not work, you can put the K back together.

If it does not work, you can build an Ignite Golden Image server on the rp7410 and that will certainly work so long as the Core OS cd is built in and the configuration files allow for 32 bit boots and installations.

SEP

[Sundar_7]

There are few guide lines to following before ignite-uxâ s make_recovery, make_tape_recovery, make_net_recovert and make_sys_image be used to clone the systems

1) First if the make_recovery or make_tape_recovery tapes are used to boot the systems, the source and the target systems should be of same architecture. This is because now ignite-UX uses different INSTALL kernels to boot depending on the architecture. The model of the system doesnâ t matter but the architecture of the system does.

The kernels are

WINSTALL - used for all the systems that are ONLY 64 bit (N, L , A etc)

INSTALL â used for systems that can run BOTH 32 and 64 bit HP-UX (K,D,R etc)

VINSTALL â used for V-Class systems

For example, the ignite-ux recovery tape created on a K-Class system cannot be used to boot a N-Class system since the kernel copied to the Ignite-UX tape is VINSTALL and the kernel WINSTALL which is used to boot N-Class systems is not available in the tape.

2) Second thing to make sure is that all the hardware enablement patches that are required in the target system should be installed in the source system. Say a recovery tape Is being created on a V2200 system to clone a V2600 system then all the hardware enablement patches required for V2600 should be installed in the V2200 system or else the system wil boot, create the kernel but when the system tries to boot from the kernel created itwill panic.

On other hand, if a V2600 ignite tape is used to clone a V2200 system then it will probably work becoz V2600 will have the newer patches which will allow the V2200 to create a bootab