1BACKUP.D(5) backupninja package BACKUP.D(5)
2
3
4
6 BACKUP.D - Action configuration files for backupninja(1).
7
8
10 /etc/backup.d/*
11
13 To preform the actual backup actions, backupninja processes each action
14 configuration file in /etc/backup.d according to the file's suffix.
15
16
17 .sh run this file as a shell script.
18
19 .rdiff backup action for rdiff-backup.
20
21 .dup backup action for duplicity.
22
23 .borg backup action for borgbackup.
24
25 .maildir backup action for slow, incremental rsyncs of tens of thou‐
26 sands of maildirs.
27
28 .mysql backup action for safe MySQL dumps.
29
30 .pgsql backup action for safe PostgreSQL dumps.
31
32 .sys backup action for general system reports and hardware infor‐
33 mation.
34
35 .svn backup action for safe backups of subversion repositories.
36
37 .trac backup action for safe backups of trac repositories.
38
39 .makecd backup action for burning backups to CD/DVD or creating ISOs.
40
41
42 These files must be owned by root and must not be world or group read‐
43 able/writable. Support for additional configuration types can be added
44 by dropping bash scripts with the name of the suffix into
45 /usr/share/backupninja.
46
47 The configuration files are processed in alphabetical order. However,
48 it is suggested that you name the config files in "sysvinit style."
49
50 For example:
51 10-local.pgsql.disabled
52 15-runthisfirst.sh
53 20-runthisnext.mysql
54 90-runthislast.rdiff
55
56 Typically, you will put a '.rdiff' config file last, so that any data‐
57 base dumps you make are included in the filesystem backup. Action con‐
58 figurations which end with .disabled are skipped.
59
60 Example templates for the action configuration files can be found in
61 /usr/share/doc/backupninja/examples. You can also use ninjahelper(1), a
62 console based "wizard" for creating backup actions.
63
64
66 By default, each configuration file is processed everyday at 01:00 (1
67 AM). This can be changed by specifying the 'when' option in a backup
68 action's config file or in the global configuration file. Special value
69 'manual' will disable scheduling for the backup action. It is possible
70 to run the backup action manually by invoking ninjahelper(1) with --run
71 command line argument.
72
73 For example:
74 when = sundays at 02:00
75 when = 30th at 22
76 when = 30 at 22:00
77 when = everyday at 01
78 when = Tuesday at 05:00
79 when = hourly
80 when = manual
81
82 These values for "when" are invalid:
83 when = tuesday at 2am
84 when = tuesday at 2
85 when = tues at 02
86
87 A configuration file will be processed at the time(s) specified by the
88 "when" option. If multiple "when" options are present, then they all
89 apply. If two configurations files are scheduled to run in the same
90 hour, then we fall back on the alphabetical ordering specified above.
91 The "when" must occur before any sections in the action configuration
92 file.
93
94
96 The file format of the action configuration files is "ini style." Sec‐
97 tions are created by using square bracket. Long lines are connected
98 with a backslash. For example:
99
100 # this is a comment
101 [fishes]
102 fish = red
103 fish = blue
104 [fruit]
105 apple = yes
106 pear = no thanks \
107 i will not have a pear.
108
109
111 backupninja(1), ninjahelper(1), backupninja.conf(5),
112
114 BACKUPNINJA was written by the riseup.net collective.
115
116
117
118riseup October 10, 2005 BACKUP.D(5)