Today I’m going to present you a simple backup script that I wrote a while ago to maintain backups for my home computers and my server.
With rsync you can do a lot of things, but in this post I’m going to explain only a simple way to copy a folder into another located:
- on the same computer (for example an external hard drive);
- on a remote computer (for example a server or a NAS).
Let’s start by examining the contents of the following script:
#|/bin/bash # croma25td simple backup script v1.0 # www.croma25td.com # croma25td at gmail dot com #user defined variables #destination folder on the local or remote machine DEST=/full/path/to/backup/directory #server parameter -- use this only if you need to backup on a remote machine (via internet or local network) #the ssh host with username@address HOSTfirstname.lastname@example.org #the ssh port, 22 by default PORT=22 #the path for the private key, with this you don't have to provide a password during the connection via ssh, usually stored in ~/.ssh/id_rsa. KEY_PATH=/root/.ssh/id_rsa #the log file, usually in /var/log LOG_FILE=/var/log/backup.log #the header for the new log echo '-----------------------------------------------------------------------------' >> $LOG_FILE date >> $LOG_FILE #rsync command list #the actual commands -- remote machine version rsync -aR --stats --delete --rsh='ssh -p '$PORT' -i '$KEY_PATH'' /etc $HOST:$DEST &>> $LOG_FILE rsync -aR --stats --delete --rsh='ssh -p '$PORT' -i '$KEY_PATH'' /home $HOST:$DEST &>> $LOG_FILE #the actual commands -- local machine version rsync -aR --stats --delete /etc $DEST &>> $LOG_FILE rsync -aR --stats --delete /home $DEST &>> $LOG_FILE
The first section of the script will contain the user defined variables:
- DEST: is the destination folder of your backup; this is the full path on your local or remote machine;
- HOST: used only if you need to save the data on a remote machine, it’s the combination of the username (with write permissions on DEST folder) on the remote machine plus the hostname; the format is: username@hostname;
- PORT: the ssh port, by default 22;
- KEY_PATH: the fullpath to the local user’s (who executes the script) private key;
- LOG_FILE: the fullpath to a logfile on the local machine (logs are usually stored in /var/log/).
The second section will print only a small header on the log file at each run of the script to separate the old outputs and know the last backup date.
The third and most important section issues the rsync commands, one per folder to backup. In this example we are going to backup two folder, /etc and /home where are stored respectively the system configuration and the user’s datas. Add one line per folder you want to backup.
Each rsync command has some parameters:
- -a: ‘archive’ activates recursion into the folders and preserve all file’s metadata;
- -R: ‘relative’ will create the same folder structure on the server;
- –stats: rsync will write, at the end of the job, a small report;
- –delete: activate the propagation of file’s deletion: if a file is deleted on the source it will be deleted even in the backup; remove this if you want to preserve all your old datas!
Then there are the connection parameters (if applicable), the source folder and the destination folder:
- to store the data on a remote machine: rsync -a –stats –delete –rsh=’ssh -p ‘$PORT’ -i ‘$KEY_PATH” /home $HOST:$DEST
We are using ssh as transfer protocol using the private key for the autentication, then we specify the source folder and the destination folder stored on the server.
- to store the data on the same local machine: rsync -a –stats –delete /home $DEST
We are telling rsync to copy the data from /home to $DEST.
At the end of the command there is the & operator that tells bash to fork the process in a subshell and >> $LOG_FILE to redirect all outputs to our log file.
Now a three-step how-to to create a private/public set of keys to authenticate via ssh:
- execute this command with the user that will launch the script (manually or with a cron):
Then follow the instructions: you have just created your public and private keys; Don’t use any passphrase if you want to execute this script with a cron job otherwise the script will wait for a password that you can’t enter… so just press enter two times to enter a blank passphrase;
- save into the server your public key so you can authenticate on it by using your private key (do not share this one with anyone!):
ssh-copy-id -i ~/.ssh/id_rsa.pub remote-host
Change remote-host to your server host;
- try to login with:
If it’s all ok it shouldn’t be necessary to write a password.
As always if you have any questions of suggestions just use the comments below 🙂