Topic: Server migration - how best to handle it?

[Rogue]

I currently have 6.0b3 running on a generic PII setup primarily as a mail server, with some family members using it for webspace/image galleries. I recently was given a dual PIII-550 Proliant 1600 to replace it.

Now comes the challenge - what is the best process to move everything from one server to the other?

I am unsure if I need to build the new server with all the various contribs first, or just a basic clean install will do? If I need to install all the contribs, how do I work out what I have installed? I've been experimenting/learning as I go, so I don't remember exactly what was installed.

I can't just relocate drives either, as I want to make use of the additional drive space in the new server (5 x 18GB drives hardware RAID5 vs 2 x 9GB drives software mirroring).

Does anyone have a HOWTO or even some simple suggestions?

[MSmith]

DISCLAIMER:  I've NEVER attempted what you're trying to do, so please think LONG and HARD before doing it!  You and only you are responsible for what happens if you try this!  Comments are welcomed from the community.  

I think what I'd do is first break the software mirroring of your existing setup, then verify that it'll boot.  On the target system, use yet another scratch drive drive and build a working Linux that can see & format your hardware RAID volume.  (Or use a Knoppix CD if it'll see the RAID array .)

Get your root and swap partitions set up & formatted on the hardware RAID volume.  Then shut down & install your booting SME drive into the system as a slave, boot from your scratch system (or, again Knoppix) and use tar or whatever utility you like to do a file-by-file copy of the SME install to the RAID volume.  Then shut down, remove the old SME drive and your scratch drive, boot from the SME 6.01 CD and do an upgrade install.

Best of luck to you ... let us know what works, eh?

[cc_skavenger]

You can try this:
http://ccskavenger.lc-usa.net/SME(E-SMITH)/Howtos/new-server-upgrade-using-rsync.html

I haven't used this method, but it sounds like a good idea.

HTH

[Anonymous]

You can try this:
http://ccskavenger.lc-usa.net/SME(E-SMITH)/Howtos/new-server-upgrade-using-rsync.html

I haven't used this method, but it sounds like a good idea.

HTH

Sounds promising, but how do I determine which contribs I've added?

Also, given that some previous contribs are not valid for the new hardware (apcups & sysmon for example - different UPS now and sysmon doesn't detect the Proliant monitoring chipset) can they just be left out?

[Boris]

Sysmon should work on the newer version, but I would probably handle it different.
First I would upgrade 6.0b3 to the 6.0.1 and update initscripts patch on the current server.
Second I would install fresh 6.0.1 and the patch on the new server to asure hardware compatibility.
After its working (basic setup), I would make a full backup of the old server and try to restore it to new server and fix if something broke by reinstalling broken add-ons (if any) or upgrading server to the same version if hardware detection needed.
If everything works, put server online replacing the old one if doesn't, leave the old server until you get it right.
The hardest part would be the full backup. Backup to desktop may not work for you, but other options (like evaluating Tapeware for 30 days) may do. You don't have to use Tapedrive for it if you don't have it. It is posible to configure application to use folder on the hard drive as backup device and since you don't have more then 9 Gb now it should not be a problem to find room for the backup.

[barryf]

Also, a couple of things about a Proliant 1600 - anaconda, the installer, seems to turn off the second processor on a dual cpu machine.  When it reboots, it sometimes thinks that the processor has failed - run the SmartStart CD again and tell it you have fixed the processor and all is fine again.  Some people have also reported that the installer hangs on detecting the USB chip on some 1600's - as the 1600 han't got a USB socket, I think they said to disable USB detection - there is a thread about it somewhere here.

Barry

[Dastardley]

If you want to install SME propperly on a PL1600 you need to do the following:

Install first SME 5.5, in this version Anaconda seems to install without problems SME on the PL1600. If you're finished, put in the cdrom from version SME 6.0 or higher. Then SME passes the point where Anaconda normaly hangs on a fresh install. In the install menu you'll get a message simular to this: previous version detected. Now you should type: "more options". You'll get the choice to do an upgrade or a fresh install. Choose fresh install. In case of a hardware RAID-configuration always install on a single disk (I've never had any problems with Smart Array-controllers in a SME-server, they seem work very well to me).

About the problem of Anaconda the following. In Red Hat Linux you can avoid Anaconda to hang by typing the following line in de install option menu:

linux apm=off lowres noapic noht nomce nousb nousbstorage skipddc

Does somebody knows how to add this line in the install configuration or to do a manual install instead of a "automatic" SME install configuration? You'll help lots off guys with this. Old PII and PIII Proliant servers are very nice machines to work with SME. It is not only the PL1600 witch has this problem you see. The PL1850R is another good example.

And yes, I've had problems with disabeling the second processor on a PL1600 dual 266 MHz, but on a dual 500 MHz no processor problems at all.

Another known problem of installing SME on Proliants is e.g.:

The Netflex TLan integrated UTP 10/100 NIC.

Some Linux versions require to disable this onboard NIC before you try to install.

A very serious problem I detected on different Proliant PII/PIII machines with a version of SME higher than 5.5 is this:

With transfering some data over the network from/to the SME-server, the connection gets lost. When I go to the server and watch the logfiles and watch the status of the SMB service, samba seems te work normaly. There are also no problems when you use the ifconfig command. Everything seems to work well, but no connection possible. I'm working/testing on that, perhaps the driver for the onboad TLan supported in SME is not good enough. I'll try to load another.

For server migration I always use a fresh install. Write down what you are installing (contribs), but before you begin copy all serverdata to a workstation/desktop pc. This is a very easy way to get the data to the ibays on the new server. It is also usefull to make a print of the settings you've changed in the config files. I've learned that if a SME-server is running well you have less system administration to do. You might forget things how to do.

Greetz,

Jasper

[Rogue]

I had no problems installing 6.0B3 on the PL1600 - no lockups and both CPUs are running. I then upgraded to 6.0.1 without issue as well.

I'm not using the onboard LAN, but rather an Adaptec dual-port card. Only one port will be used initially, with the second port reserved for a community wireless LAN connection in the coming months.

Now I'm working on creating a list of contribs I want to include on the new server, and will build it up from a clean install. I can transfer the user data easily enough, and it's probably better to go back to a clean slate. I'll keep the existing server around as a scratch-pad for future experiments.