Backing up your files with rsync
Backing up files on a regular basis is an integral part of administering your server.
One way is to download each and every file when you want to save them. However, rsync makes the task a lot easier as it only downloads files that have changed - saving time and bandwidth.
Installing rsync is as simple as implementing your OS's package manager such as:
sudo aptitude install rsync ... sudo emerge rsync ... sudo yum install rsync
Do remember that if you are downloading files to another system, both will require rsync to be installed.
Very little to do here expect to establish where the saved files will be located.
In this example, I am going to backup my main Cloud Server home directory to another server.
As a rule (and one I stick to very closely), we don't upload and download anything without some encryption in place. As such we will be using the SSH protocol with rsync to ensure no one else can sniff out the data being transferred.
What does this mean? Well, if you want to automate your backups, you will need to ensure the destination server (where the backup directory is) has access to the originating server.
In my case, I have setup ssh keys so I don't need to enter a password each time I attempt to rsync my home folder. It's perfectly fine not to do it that way, but you will need to enter the password each time you rsync.
So on the destination server, the command I would give is as follows:
rsync -e 'ssh -p 30000' -avl --delete --stats --progress firstname.lastname@example.org:/home/demo /backup
Let's go through the command in order:
-e 'ssh -p 30000': this ensures rsync uses the SSH protocol and sets the port.
-avl: This contains three options;
(a) is archive mode which basically keep the permission settings for the files. (v) is verbose mode. You can leave it out or increase it by appending two v's (-vv). (l) preserves any links you may have created.
--delete: deletes files from the destination folder that are no longer required (i.e. they have been deleted from the folder being backed up).
--stats: Adds a little more output regarding the file transfer status.
--progress: shows the progress of each file transfer. Can be useful to know if you have large files being backup up.
email@example.com:/home/demo: The originating folders to backup.
The syntax here is very important - naturally you need the username and IP address of the originating server - but note in this example there is no trailing slash (/).
If you leave the trailing slash off, the named folder and contents will be downloaded. So in this case I would have a folder called 'demo' in my backup directory.
If I added the trailing slash (firstname.lastname@example.org:/home/demo/) then I would have the contents of demo in my backup. So I may have folders called 'public_html' or 'configs' or 'bin' and so on.
/backup/: Identifies the folder on the backup server to place the files.
So from the command above, my storage server would start to output something like this:
receiving file list ... 31345 files to consider ./ tuning-primer.sh 42596 100% 533.30kB/s 0:00:00 (xfer#2, to-check=31331/31345) bin/ bin/Backup 618 100% 7.74kB/s 0:00:00 (xfer#3, to-check=31310/31345) bin/Search 455 100% 5.70kB/s 0:00:00 (xfer#4, to-check=31309/31345) configs/ configs/php.ini 114 100% 1.43kB/s 0:00:00 (xfer#5, to-check=31307/31345) public_html/ ... ...
As you can see, it receives a list of files (31,345 of them) and, for the first run, downloads them all.
Running rsync again will only download files that have changed so, depending on how busy your home directory is, a much smaller download will be conducted.
This was a quick introduction to rsync. The command shown is a simple but effective and secure means of creating an incremental backup of your files.
The next articles will concentrate on some more options such as excluding files or directories from the backup and creating a script to automate the process and put the backups into daily folders.
--Kelly Koehn 13:30, 2 April 2009 (CDT)
© 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
See license specifics and DISCLAIMER