Koozali.org: home of the SME Server

migrate to new server best practice?

Offline jahlewis

  • *
  • 151
  • +0/-0
    • http://www.arachnerd.com/
migrate to new server best practice?
« on: January 29, 2005, 03:39:31 AM »
hi all,

I've got a 6.0.1 server (single drive)with a bunch of contribs, yum upgrades and additional packages that is running in production mode very successfully.

I'd like to migrate it to a faster box, with new, larger hard drives (sw raid).

What is the best way to do this?

As I see it there are two options

1) backup using backup to desktop script
2) build new box, upgrade and install contribs
3) restore backup

or

1) backup to tape
2) build new box, upgrade, install contribs
3) restore from tape

My server has a bunch of sql databases, live mail queue's and postoffices etc.

I'm looking for some best practices/suggestions as to how to make this process as least painful as possible.  I'm willing to write a howto if you all point me in the right direction.

Should I wait until 6.5 is out, and upgrade to a 6.5 box, or do it now with 6.0.1?

Many thanks!
............

cc_skavenger

Re: migrate to new server best practice?
« Reply #1 on: January 29, 2005, 05:33:56 AM »
Quote from: "jahlewis"

1) backup using backup to desktop script
2) build new box, upgrade and install contribs
3) restore backup


This is the only way I have had a successful restore.  I had so many problems with tape backups....

But, I would change the process to:

1) backup using backup to desktop script
2) build new box
3) restore backup
4) upgrade and install contribs

You are asking for trouble if you do it in the order you listed.  The restore will overwrite several files and might leave your server in a bad state.

Just my opinion and good luck.

Offline smeghead

  • *
  • 563
  • +0/-0
migrate to new server best practice?
« Reply #2 on: January 29, 2005, 11:41:24 AM »
.. if you scout around the forums a bit you should find an rsync method fo doing what you want - on last review it seemed to be fairly robust and well thought out ..
..................

patrick

migrate to new server best practice?
« Reply #3 on: January 29, 2005, 02:33:17 PM »
That would be mine.

Process is:

build new box, install contribs you want then run the script:

http://www.ibiblio.org/pub/Linux/distributions/smeserver/contribs/ptehvand/howtos/rsyncmigrate.html

Cheers

Patrick (elSpike) out.

Offline jahlewis

  • *
  • 151
  • +0/-0
    • http://www.arachnerd.com/
migrate to new server best practice?
« Reply #4 on: January 29, 2005, 02:50:21 PM »
awesome!  I'll try this and report back.

I see you don't include any items in var (like mail)...

What does the backup to desktop script backup?  What does the tape backup script backup?

Thanks!
............

patrick

migrate to new server best practice?
« Reply #5 on: January 29, 2005, 03:02:44 PM »
That is everything in the desktop backup.

You can add things like /var/mysql and /etc/samba for machine accounts if you like. I need to update that list of files after doing a migration of a machine with 800 user accounts about 5 weeks ago.

It works, Ive done it on production machines a number of times

p.

Offline jahlewis

  • *
  • 151
  • +0/-0
    • http://www.arachnerd.com/
migrate to new server best practice?
« Reply #6 on: January 29, 2005, 04:01:13 PM »
seriously, I can't thank you enough for this approach.  I'll also work on a list of files/directories and we can compare...

Do you do it line by line, or create a script with all the lines?

-JL
............

patrick

migrate to new server best practice?
« Reply #7 on: January 29, 2005, 05:56:21 PM »
I usually do it line by line, but a script would do it.

I do it line by line as im usually doing close to 100 Gb transfers.
p.