In the previous article we looked at the conditions we want to match on the origin and destination servers and ways to prepare the origin server for a more efficient migration. Now we’ll start the actual process of migrating your Linux server.
With the prep work done let’s look at the tool we’ll use to copy the files: rsync.
The rsync program lets you copy a directory from one server to another over an SSH connection. It can optionally delete any files in the destination folder that aren’t in the original folder and lets you skip over subdirectories you don’t want to copy. Best of all, rsync only copies files that are different in the origin and destination folders. You can run an rsync more than once without worrying about unnecessary overhead from repeat copies.
We’ll leverage all those features of rsync. The trick lies in knowing what files and directories need to be left alone on the destination server. Then we can let rsync copy the rest.
Luckily rsync can work with an “exclude file” - a list of directories and files that rsync should overlook when performing a sync.
You’ll use the exclude file to list files and directories specific to the original server that wouldn’t be meaningful if copied or that might change during the copy if your server is live during the migration. You just need to create a text file with the list of those items, one on each line.
Do consider your excludes carefully. You don’t want to sync any files that reference or could affect the IP address of the destination server because they could make it difficult to connect to the server or prevent services from starting.
A simple exclude file that covers a variety of Linux distributions can look like this:
/boot /proc /sys /tmp /dev /var/lock /etc/fstab /etc/mtab /etc/resolv.conf /etc/conf.d/net /etc/network/interfaces /etc/networks /etc/sysconfig/network* /etc/sysconfig/hwconf /etc/sysconfig/ip6tables-config /etc/sysconfig/kernel /etc/hostname /etc/HOSTNAME /etc/hosts /etc/modprobe* /etc/modules /net /lib/modules /etc/rc.conf /usr/share/nova-agent* /usr/sbin/nova-agent* /etc/init.d/nova-agent*
Note that it’s okay if you list something in the exclude file that doesn’t exist on your system. Rsync won’t care because rsync was going to ignore that item anyway.
Carefully weigh which files will or won’t included in the exclude file, and make note of any files that aren’t being rsynced but may need to be updated on the target server.
The most important excludes are the ones that reference hardware and system files that keep track of the server’s status while it’s running. The destination server should already have those directories and config files in place so they shouldn’t be overwritten.
If you have a database that’s being regularly accessed and changed you’ll want to leave it out of the sync until the very end. Otherwise your rsync runs will need to recopy the database each time. Get the rest of the system out of the way then copy the database at the end (preferably after you’ve stopped the database service).
The same holds true for directories that hold application state files or cache files. If they change often they introduce extra work for the first sync. Best to put them in the exclude file at first then remove them when you’re ready to complete the migration.
Now we test rsync to make sure everything is in order. Make note of the port sshd is listening to on the destination server as well as the name of the exclude file.
If ssh is running on port 30000 and you named your exclude file “exclude.txt” in the home directory of user “demo”, you would kick off the sync test by running:
sudo rsync -e 'ssh -p 30000' --dry-run -azPx --delete-after --exclude-from="/home/demo/exclude.txt" / email@example.com:/
Real short summary of the above command: It pretends to copy everything from “/” on the original server to the same place on the destination server so you can make sure it doesn’t have a problem making the connection.
Change the "ssh -p 30000’ part to match the destination’s ssh port.
The “–dry-run” flag is the bit that tells rsync to go through the motions but not actually copy anything yet.
The “-azPx” stuff tells rsync to try and keep everything the same as it was on the original server, compress it in transit to save bandwidth, show its progress during the copy, keep partially-transferred files if interrupted, and don’t cross filesystems (e.g. don’t copy files from remotely mounted filesystems).
The “–delete-after” flag tells rsync not to delete anything from the destination until all the copying is done.
The “–exclude-from” value tells rsync to use your exclude file, and where to find it.
The last two items are the actual arguments to rsync. First is the directory we’re copying from and the following argument is the destination. In our case the origin is “/”. The destination is in the form “username@ip-address:destination-directory”. So the above command would connect to the server at 18.104.22.168 as root then copy the files using “/” as the destination for the files. Don’t forget the colon.
Rsync will ask you for the password to connect just as it would if you were trying to ssh to the destination server (which, technically, you are).
Once it’s done look over the list of directories to make sure it doesn’t plan on copying anything you should exclude.
If all went well (as in, there were no errors you need to puzzle out) we’re ready to start copying. Again using ssh on port 30000 for the example, we would run:
sudo rsync -e 'ssh -p 30000' -azPx --delete-after --exclude-from="/home/demo/exclude.txt" / firstname.lastname@example.org:/
Note that it’s the same command as before without the “–dry-run” flag.
Now…wait. How long it will take depends on factors like how much disk space you’re using and how many files are being transferred. You’ll see a list of what’s being copied scroll down the screen so you can get an idea of the sync’s progress.
Should the sync be interrupted you can just run the same command again and it will pick up where it left off. Make sure you don’t reboot the destination server until you’re completely done with the copy. A partially-migrated server will probably get very confused if it tries to reboot.
Doing one pass got the more static files over to the new server. That’s good, but that may not be everything you needed to copy. An active database or a directory where a lot of files get created and deleted may have been copied but changed already. Or, more practically, they may have been in your exclude file.
To get those last files you’ll want to bring the services that use them down. That way you know the entire file will be migrated with no changes made after your last sync.
Edit your exclude file to remove references to the busy files you were holding off on then run the rsync command again.
Once you’re satisfied that you’ve got a full sync done take a last look around the destination server. Make any necessary tweaks to the new server. For example, if you use our sample exclude file the hostname of the destination server won’t change. If you need to set that to match the original now would be the time to make that manual edit.
If you’re running Arch Linux check the /etc/rc.conf file. Since that file contains networking configuration we put it in our sample exclude file so it wouldn’t be migrated. You’ll need to manually edit rc.conf to set the services that will start at boot time (the “DAEMONS” value).
It’s time to reboot the destination server and see how it looks. Ideally it will look just like the original server and will be running the same services when it comes up.
Note that the new server will be using the same sshd configuration as the old server as well as the same SSH host signature. You probably need to delete any saved key for the new server from the “~/.ssh/known_hosts” file or equivalent on your desktop’s operating system. Otherwise you’ll get a warning about a changed server key or you might be prevented from connecting at all.
The users and passwords on the new server will also match those of the old server. That includes changing the root password.
Thorough testing is definitely advised if you’re migrating a production server. Once your testing is done you can change your DNS to point to the new server. You should also make sure any other servers you had pointing to services on the old server are updated. And don’t forget to configure backups for the new instance!
In case it wasn’t emphasized enough, test the new server before putting it into production. We’ve tried to cover all the possibilities but it’s always possible a network config file slipped through or that one of the files you moved referred to the old IP address and needs to be updated. It’s good to catch those issues before letting the rest of the world access your services.
The next article examines alternative approaches to server migrations in case a live rsync isn’t the best choice for your environment.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License