Igniting from a D-class to a K-class

[Valisha Bradford]

Has anyone ever ignited a D-class server running 11.0 and restored it on a K-class server? I will be doing this at an offsite disaster recovery facility. Once I use the ignite tape to restore the K-class, what should I look out for? Below is my gameplan.
1. Use the ignite tape to recover the K-class
2. Once server is up, do a ioinit -i -r to
install special files and reboot
3. Once server is back up, use swinstall to
install missing drivers.

Does this sound right to anyone?

Thanks in advance.

[Pete Randall · Accepted solution]

Valisha,

That's it in a nutshell. You need to watch out for device file differences and driver differences but you know that and have it covered. Sounds good to me, but the reason we practice these things is to discover the little things that may have slipped past us.

Good luck,


Pete

[Martin Johnson]

First off, you won't be able to automatically boot the Ignite tape on the K. Ignite for the D uses a different boot file than the K.

Working out the differences is not trivial. It may be easier to do a cold install of the OS on the K and restore everything (except /dev) for backup.

HTH
Marty

[Elena Leontieva]

This doc should answer most of your questions.
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000064128875

Elena.

[Pete Randall]

In response to Marty's concern, I quote from Elena's link concerning the different kernels used:

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


I still think you're fine, Valisha.


Pete

[Bryan D. Quinn]

Hello,

I can vouch for this scenario. I have done it sucessfully many times. Even offsite at a DR test. The Ignite will cancel out of Batch Mode installation because of the disks device file differences, but you massage it a little manually and it will be on it's way.

Just make sure when it cancels out of Batch Mode to go through and check your file system sizes, it will most likely want you to choose a new boot disk manually. Do that and make sure your file system sizes and swap are correct.

When you are satisfied, just kick it off and let it go. It will be fine.

Hope this helps!
-Bryan

[Steven E. Protter]

I think you have the bases covered quite nicely.

Please report results. Inquiring minds want to know.

SEP

[James R. Ferguson]

Hi:

This will work just fine. I have the same situation during my own disaster recovery exercises.

I Ignite the K-box with the recovery tape and configure the built-in LAN card ('ifconfig') with a valid IPaddress. Having done this I can can run 'swinstall' to install the network and/or disk drivers I need. 'swinstall' is down-right fussy about having a viable network that I've found this direction to be the most straightforward. Once I have the network drivers I want/need, I simply manually edit 'etc/rc.config.d/netconf' to my needs.

Ignite recovery will automatically reboot twice so there should be no need to manually issue an 'ioinit'.
Regards!

...JRF...

[Martin Johnson]

Pete,

You are right. Went back to my notes - we had problems using an Ignite tape from a K to ignite a V class system.

Sorry for the Senior Moment
Marty

[Tim D Fulford]

Just one bit of advice. I have successfully used Ignite to migrate the OS cross platforms. I did find that having the application disks handy is a good idea as when I did it the LAN card drivers (& tachyon drivers too, but I expected that) were not on the source machine.

Regards

Tim