Changes between Version 4 and Version 5 of faq/backup-setup


Ignore:
Timestamp:
Jul 10, 2008, 11:44:08 AM (13 years ago)
Author:
Jack Aponte
Comment:

Changed directory variable to make it more simple; changed position of trickle information in instructions to make sense in terms of a typical user's workflow when setting up backups; added trickle cron job info.

Legend:

Unmodified
Added
Removed
Modified
  • faq/backup-setup

    v4 v5  
    66
    77We recommend that you use backupninja and rdiff-backup. Below are instructions for how to get started with these two programs.
    8 
    9 NOTE: in it's current release backupninja has no internal way to limit bandwidth (bandwidth limiting will be available in future releases). Therefore you should run it through [http://www.monkey.org/~marius/trickle/ trickle]. dkg explains it with:
    10 
    11 {{{
    12 Say you want to limit backupninja 50Kbps down and 70Kbps up. Instead of running
    13 
    14 backupninja -n
    15 
    16 you can run
    17 
    18 trickle -d 50 -u 70 backupninja -n
    19 }}}
    208
    219If you are not running Debian, please check out the respective web sites for  backupninja and rdiff-backup to download the programs ([http://dev.riseup.net/backupninja/ http://dev.riseup.net/backupninja] and [http://www.nongnu.org/rdiff-backup/ http://www.nongnu.org/rdiff-backup]).
     
    5846
    5947
    60 # an optional subdirectory below 'directory' (see [dest])
     48# an optional subdirectory below 'directory' (see [dest]).
     49# This should be set to the name of the particular server you're backing up
     50# in order to distinguish between multiple server backups.
    6151label = SERVERNAME
    6252
     
    6959# files to include in the backup
    7060# (supports globbing with '*')
     61# You can add additional lines to back up additional files or directories.
    7162include = /etc
    7263include = /var/log
     
    9182
    9283# put the backups under this directory
    93 directory = /home/members/MEMBERNAME/backups/
     84directory = backups/
    9485
    9586# make the files owned by this user
     
    109100}}}
    110101
    111 (t is test, n is now, d is debug)
     102(t is test and tells backupninja to simply test the backup procedure without actually backing up the files; n is now, which tells backupninja to ignore its regular schedule and run right now; d is debug, which tells backupninja to give detailed feedback on what it's doing and any errors it encounters.)
     103
     104NOTE: in it's current release backupninja has no internal way to limit bandwidth (bandwidth limiting will be available in future releases). There are two good reasons for setting bandwidth limits: so that your internet connection's bandwidth isn't completely monopolized while the backup is running, and so that you don't monopolize May First's bandwidth and make it harder for others to do backups at the same time as you. Therefore, you should run it through [http://www.monkey.org/~marius/trickle/ trickle]. dkg explains it with:
     105
     106{{{
     107Say you want to limit backupninja 50Kbps down and 70Kbps up. Instead of running
     108
     109backupninja -n
     110
     111you can run
     112
     113trickle -d 50 -u 70 backupninja -n
     114}}}
     115
     116Since you won't usually be running backupninja manually, you should also change backupninja's cron job to use trickle. By default in Debian, the cron job will be found in /etc/cron.d/backupninja. You should change the cron job to look something like this:
     117
     118{{{
     119# /etc/cron.d/backupninja -- cron tab entry for package backupninja
     120
     121PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
     122
     123# run backupninja every hour on the hour
     1240 * * * * root if [ -x /usr/sbin/backupninja ]; then /usr/bin/trickle -d 50 -u 70 /usr/sbin/backupninja; fi
     125}}}
    112126
    113127A few additional thoughts from abh: