3 beethoven.debian.org alias backup.debian.org is Debian's backup machine.
5 == Backup organisation ==
7 {{{/org/backup.debian.org}}} contains two directories, {{{staging}}} and
8 {{{backup}}}. The latter contains the backup and is organised in directories
9 with date directories that contain all the files from that particular day. The
10 number of kept copies is configured in files in {{{/etc/da-backup-manager/}}}.
12 The {{{/staging/}}} directory is used by the clients, i.e. the .debian.org
13 hosts that have something valuable to backup. The contents of the particular
14 directories is pushed from root to root@backup.debian.org via rsync via a
15 restricted SSH session based on key-authentication.
20 /org/backup.debian.org/staging/
25 /org/backup.debian.org/backup/
39 == Adding new backup directories ==
41 * install da-backup on the client
42 * create a crontab that runs da-backup daily at some convenient time
43 * configure the directories in {{{/etc/da-backup}}}
44 * install the public host key of the server with a proper command in
45 puppet {{{modules/ssh/templates/authorized_keys.erb}}} for beethoven. Do a puppetrun on beethoven.
46 (This might get done automatically eventually.)
47 * configure how many copies of the directory should be kept in
48 {{{/etc/da-backup-manager/}}}
49 * run {{{da-backup -v}}} on the client to see if it all works.
52 * Backup items should be called {{{<host>/<directory>}}}.
53 Historically we also used {{{services/<servicename>}}}.
55 == Consistency checks ==
57 * Run {{{sudo -u nagios /usr/lib/nagios/plugins/dsa-check-dabackup-server}}}