Distributed auto-updatable backup infrastructure.
$ sudo apt-get install git wget rsync
Download and install a base Cygwin system: https://www.cygwin.com/install.html
Important: Some mirrors contain old packages. In our tests, mirrors.kernel.org worked well.
Now install dependencies of the script running CMD (Command Prompt):
> setup-x86_64.exe -q -P git,wget,rsync,cron,cygrunsrv
Now open a Cygwin terminal with administrative rights (right-click on icon -> Run as administrator) and execute the pre-installed script cron-config:
$ cron-config
Do you want to install the cron daemon as a service? (yes/no) yes
Enter the value of CYGWIN for the daemon: [ ] ntsec
Do you want the cron daemon to run as yourself? (yes/no) no
are you using the cyglsa package ? (yes/no) no
Please enter the password for user 'cyg_server': SOMEPASSWORD
Reenter: SOMEPASSWORD
... no problem found.
Note: Password must correspond to the Services GUI -> Properties -> Logon.
You may also add cygwin to the path: System Properties -> Advanced -> Environment Variables -> Path -> Add "c:\cygwin64\bin"
Run the "Services" GUI windows app to check that the "Cron daemon" task is running.
Every machine has a name within the infrastructure backup. Let's see an example for the host arquimedes, which has name arquimedes-linux. When performing a backup, it would first get configuration files from configs/arquimedes-linux:
- configs/arquimedes-linux/backup:
RSYNC_MODULE FREQUENCY PATH1 PATH2 ... PATH3 - configs/arquimedes-linux/cron: Crontab entry.
So in this case, arquimedes uses rsync module arquimedes. To get the backup host, the script would now check the file configs/backup-hosts. In this case, it would match the entry arquimedes faraday, so the backup rsync endpoint is faraday::arquimedes.
rsyncd.conf must be configured on the backup server for this module:
[arquimedes]
path = /nas/backup/computers/arquimedes
hosts allow = arquimedes.cnb.csic.es
write only = true
read only = false
list = false
use chroot = true
Previously, update servers were used to store all the configuration files, but now we use directly this GitHub repository except for sensitive data that cannot be made public (for example, the email credentials).
The script auto-updates itself and the configuration files pulling from this GitHub project (check cron_scripts/rsync_backup_linux, variables repo_url/repo_branch. Note that if there is a bug with the self-replacement code, you'll have to update manually the script on all clients.
If the script fails, it will try to send an email to cnb DOT notifications AT gmail.com. For this to work, you'll need a sendemail.auth file (see Setup section) on the backup servers and the package sendemail installed on every client.
- On clients:
/var/log/rsync_backup.log - On backup servers:
/path/to/client/backup/rsync_backup.log
Create a file with the credentials for sendemail (Gmail account):
$ echo "EMAIL PASSWORD" > /etc/sysman/backup/sendemail.auth
For existing clients to get the new script you will also need to copy the new script:
$ git clone https://github.com/EyeSeeTea/i2pc-backup
$ cp i2pc-backup/cron_scripts/rsync_backup_linux /etc/sysman/backup
The update mechanism should get the new script from the update servers without any additional action.
You will need to install the script and the sysconfig file:
$ git clone https://github.com/EyeSeeTea/i2pc-backup
$ sudo i2pc-backup/cron_scripts/rsync_backup_linux install
Make sure you have also entries for configs/HOST-linux and configs/backup-hosts.
To finish the installation you must execute /etc/cron_scripts/rsync_backup_linux at least once so that the cronjob is configured correctly.