Gotchas when migrating users to a new Linux server?

Hello all --

I am replacing a server we have in work with a new one I built.  The current server is running Fedora Core 6, and the newly-built server is running Fedora 8.  The current server is primarily acting as a fileserver via Samba, allowing centralized folders for all the WinXP machines in the lab, and each of these XP machines is backed up to the server every night.

Anyway, I've never transferred user settings (et. al) from one server to an entirely different one.  Also, I'm not proud, so I'll ask -- are there any "gotchas" I should be aware of when I undertake this move?

There are instructions at that look fairily comprehensive, and I know I'll need to transfer Samba users and the samba.conf file.  I'm also planning on using rsync to copy the /home directories from the old server to the new server via the network, so if there are any of the myriad rsync switches I should use or avoid, I'd appreciate the heads-up.

Basically, never having done this before, I'm trying to avoid the forehead-slapping moment when I realize I've forgotten something...

Thanks for all advice.
LVL 17
Who is Participating?
arrkerr1024Connect With a Mentor Commented:
The archive switch means "preserver everything", like you're making an archive in the more conceptual sense - it doesn't mean make something like a tarball.

As far as comfort, thats the nice thing about fedora and redhat/centos, fedora is just the test bed for redhat - so they're almost identical except for newer packages in fedora - the installer is the same, package names are the same, etc.

The compression flag just compresses stuff when it is sent.  So it reduces bandwidth, but uses the CPU more.  If you're on a local network, don't use it.  If you're going over a slower link, especially if you have a fast processor, then it'd be worth using.

It doesn't matter at all which way you go.  A push and a pull will do exactly the same thing.

As far as selinux, you might have found your own problem.  The answer is no - it seems you need the latest version which supports the -X flag, and you need it on both ends.  Otherwise the copy will just inherit whatever settings the parent has.
Nope, no gotchas - at least not for what you're doing.  Thats one of the beautiful things about linux/unix.  Just make sure that you copy the /etc/shadow, /etc/passwd, and /etc/group files over as outlined in that web page - excluding the system accounts.  Then just "rsync -a", the archive, -a, flag will preserve everything for you - make sure you use it.   You could also use -z to compress data if you want.

BTW, you might want to think about using CentOS-5 instead of Fedora.  It stays current for a lot longer, so you don't have to do these upgrades just to keep getting updates.  If you don't know, CentOS is just a free re-build of RedHat Enterprise.  Since they try to keep it stable and don't upgrade major versions of things it can get out of date, especially for graphical things, but for servers thats what you want.
mjcoyneAuthor Commented:
I considered switching to CentOS; I was aware of it.  It actually would be the sensible move, considering this is a working server and stabilty should be a priority goal, but I've got Fedora on my server at home, and I'm comfortable with it.  Plus, I'm a bit of a hacker, and I like things bleeding edge...:).

As for rsync,  the archive switch doesn't create an "archive" (similar to tar or gzip) does it?  I'm just trying to recreate the files on the new machine faithfully and ready for immediate use.  Ideally, I'd like to do the rsync transfer and pull the plug on the old machine.

Does the compression flag with rsync just save bandwith on the transfer, or is it for creating an archive (for lack of a better term), again like compression utilities?

Will SELinux file labeling be preserved with the rsync transfer, or will I need to relabel the new machine?

Final question on the rsync transfer -- is it better to run rsync on the new machine, and "pull" the files over, or run it on the old machine, and "push" the files to the new machine?

Thanks for your help...
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

mjcoyneAuthor Commented:
Okay, rsync shouldn't be a problem.  The server in work has rsync-2.6.9-2.fc6 on it, according to the RPM database.  I can't check the new server from here (I'm at work, it's at my house waiting for me to haul it in here and pull the trigger on the replacement), but think it has 2.6.9-3.2 on it.

Maybe I'll just dig up my crossover cable and hook the machines together that way, rather than over a LAN...?
mjcoyneAuthor Commented:
Tank you, arrkerr1024.  Things went very smoothly.
mjcoyneAuthor Commented:
That should, of course say "Thank you, arrkerr1024. Things went very smoothly." :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.