Migrating system to newer SuSE linux ver

[TheHiveMind]

We have decided to migrate our system onto better hardware, aswell as updated versions for almost everything (Linux/Perl/Mysql etc)

My question is: How would the techies accomplish this easily?

We will want to migrate the following intact if possible:
-Files
-Directories
-Users/permissions
-Databases
-Cron Jobs

Would the most effective way be some kind of a restore on the new machine?

Im asking this question because I will end up having to deal with any problems as I will be testing the system, to make sure everything that needs to be there, is there, and to make sure our scripts are compatilbe with all the different version changes.

Is there anything else I need to watch out for?
I have never done this, and I will not be responsible for moving the data, but I am responsible for everything that cannot be done by the person who is simply moving the data, so I need to know the capabilities and what can/cannot be done to plan ahead.

Certain programs and modules will need to be reinstalled and configured by them, what else is not plausible? What else cannot simply be transferred?

Any help is appreciated.

 

[Other Pineapple Smurf]

You would just clone the existing drive to the new one and then do an update. This is not Windows so you will not get a blue screen of death 'cause your hardware changed.

 

[MyWorld]

Doesn't SuSE come with an upgrade option in the installation menu?

Back up the system:
http://mybroadband.co.za/vb/showpost.php?p=2132711&postcount=10

Restore that onto the new hard drive (via the network, LiveCD, just as you see it simple and fit), pop in the new SuSE DVD/CD after the restore and proceed to update the installation.

Just remember if it asks if you towards the end if you want to reinstall GRUB, say yes.

 

[The_Unbeliever]

Just to be on the safe side - clone that hard drive, keep the original, and upgrade the newer one.

If it borks out, you will still have a working (older) version.

It won't hurt to make sure that the binary, user and root files all go into the same directories...

(for example SCO Openserver uses a totally different layout than OpenSuSE...)

 

[TheHiveMind]

I would love a simple solution like cloning, unfortunately we will be implementing version upgrades for linux, mysql and perl. I don't see how I can accomplish that with cloning.
Is there a way?

 

[The_Unbeliever]

What OS is the old system running at present?

And the target (planned) is OpenSuSE 11?

You can also register at www.unix.com - and ask there. If you're unable to, I'll proxy for you.

 

[TheHiveMind]

The old system is SuSE Linux 7.3 (i386) - Kernel 2.4.10-4GB (0).

Im not sure yet which version of Suse we will be using yet, Im still trying to get that info, but it should be one of the latest versions.

 

[fskmh]

I would love a simple solution like cloning, unfortunately we will be implementing version upgrades for linux, mysql and perl. I don't see how I can accomplish that with cloning.
Is there a way?

I've copied mysql 4.x tables over to a machine running mysql 5.x before.
I would suggest a parallel installation; install the new box, copy the mysql tables over and see what the issues are. (By this I mean literally tarring /var/lib/mysql, untarring on new box, checking perms and firing up mysql.)

I can't see an issue with running your old perl scripts on a newer version of perl, unless we're talking about cgi scripts here, I've had a situation where an upgrade of perl broke a cgi script. If you have any php 4.x integration with mysql stuff then you might also be in for some fun when you move to php 5.x.

Bottom line, do not nuke the current box until you've tested everything on a parallel installation.