Partial Clone: Building a server based on another

[Travis Paakki_1]

I am trying to build a server to serve as a replacement for the first. The first server, currently in production, makes use of DTC's, and has 30 or so printers. The new server has a completely different hardware layout but will make use of all the existing DTC's and peripherals.

I have built the replacement box using a new logical volume layout, so a direct copy wont work. I have the os installed, the db installed, and the application. I was hoping that someone can give me some direction on the best path forward for syncing the peripherals. Is there any path as straight-forward as just copying a few files?

The hope is to take this replacement box out on site, shut down the old server, plug in the new one, change the IP to that of the first box and resume normal operation.

[John Poff]

Hi,

If the O/S level of the machines is the same I would suggest using Ignite. It is certainly the best tool for cloning systems. You mentioned you have a new logical volume layout. If you are referring to a non-vg00 volume group, you can keep your existing work. Just vgexport the ones you have created, make an Ignite tape of your old server, clone the new server with the Ignite tape, and then vgimport your volume groups. If you are referring to your root volume group, you can specify the logical volume layout and size when you Ignite the second box, so you still would be in good shape.

There are just too many fine details in the operating system to worry with trying to get it all right manually.

JP

[Michael Steele_2]

I'd go along with John's suggestion about using ignite clones. Just make sure the server classes are the same. L's and N's clone, most of the K's clone amongst themselves, D's are altogether separate and V class are also by themselves.

If you run into problems cloning then strip the box of all peripherals including plug in cards and then load the O/S. Peripherals can be loaded in once the O/S is installed.

This last comment sound like it might be what you're after but it???s only to a point. The cloning process is more specific to the patch levels, drivers and transferring the state of one server onto another server. The peripherals are all handled by the kernel and the O/S during reboot so all the peripheral drivers should transfer cleanly.

[Michael Tully]

The latest version of ignite allows creation from a different hardware model. There are some pre-requisites.

The latest version of ignite can be found here:
http://www.software.hp.com/products/IUX/download.html

from the man page of "make_tape_recovery"

will allow you to interact with the installation and make any changes necessary (such as changing which disks to use, hostname and IP address). If you do not use the -i option to create the tape, you will be given 10 seconds when using the recovery tape to stop the automatic installation. The procedure below describes this situation.

When cloning systems, it is very important to change the networking information to avoid IP-address conflicts between the original system
and the new system. You must interact with the installation to make these changes.

Using a recovery tape to clone systems will only work if the two systems are capable of running the same software configuration. This
means that the source system must contain a version of HP-UX with all necessary patches and driver software required by the clone system.

If the two systems are different hardware models, a new kernel will automatically be built to suit the new hardware. If the two systems are the same model, the clone will by default use the kernel from the original system. You may force a kernel to be built by using the "Additional" screen in the Advanced user interface to set the "Cloning to different HW?" selector to TRUE.

HTH
Michael

[Travis Paakki_1]

All,

Actually I was afraid that I would end up getting the canned "Ignite" response, and was hoping that I clarified that it was not an option with the description of the newer versus the older system, which, rereading it, I apparently did not. Sorry, one of the many benefits of sleep depravation.

I am going from a D class running 11.0 32bit and 2 external ds2100's to a RP5470 running 11.0 64bit and an external VA7400. The new server, is built, os and database wise, the logical volumes are in place and the database is linked to them.

What I really need a way to get the new server talking to the old peripherals, and was hoping for something far better than adding them manually. The site does make use of DTC's and has almost 50 printers.

A checklist from someone who had done this during the pre-ignite days would be great.

Thanks

[Steven E. Protter]

It will be delicate, but Ignite does have the ability to handle different hardware. If you make the orginal box the Ignite server you can set up a profile for the new server that includes the new disk and logical volume layout.

When setting up the profile, Ignite gets disk information off the target server.

As far as going 32 bit to 64 bit, I've not tried that. That could be a barrier that forces you to go with a cold install.

You've not listed your OS. If your original server is 10.20 or even 11.00, it might pay to take a different approach, cold install of 11.11 and migrate your applicattions and printer setup one by one.

SEP

[John Meissner]

At my company we use Ignite for this. Ignite allow you to recover to different hardware. When you recover on the new server you can specify different lvol sizes. I've done this MANY times while preparing for a disaster recovery test.