- In the authorized_keys2 on the source system, I didn't include the from="kitty" bit as the destination PC that I'm pulling from has a dynamic IP
- I included --print-statistics in the cron job's command line, redirected the output to a logfile
- I setup the three config files/scripts setup to have LogWatch tell me the daily summary of the rdiff-backup results. i.e.:
- /etc/log.d/conf/logfiles/nyc-backup.conf
- /etc/log.d/conf/services/nyc-backup.conf
- /etc/log.d/scripts/services/nyc-backup
- /etc/log.d/conf/logfiles/nyc-backup.conf
2007-07-04
Remote backups with rdiff-backup
I set this up a while back, but I needed to make some notes on my setup of rdiff-backup that backs up my colo'd PC to my home fileserver. I've been using it for more than 3 months and it has done a great job - space efficient, time efficient and bandwidth light. I followed the recommended unattended HOWTO and it was easy to setup - even with different OSes (Solaris x86 vs. CentOS), versions of ssh and versions of rdiff-backup itself. Only modifications were:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment