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