1 .\" Hey, EMACS: -*- nroff -*-
2 .\" First parameter, NAME, should be all caps
3 .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
4 .\" other parameters are allowed: see man(7), man(1)
5 .TH BACKUP.D 5 "October 10, 2005" "riseup" "backupninja package"
7 BACKUP.D \- Action configuration files for \fBbackupninja(1)\fP.
9 .\" Please adjust this date whenever revising the manpage.
11 .\" Some roff macros, for reference:
12 .\" .nh disable hyphenation
13 .\" .hy enable hyphenation
14 .\" .ad l left justify
15 .\" .ad b justify to both left and right margins
16 .\" .nf disable filling
17 .\" .fi enable filling
18 .\" .br insert line break
19 .\" .sp <n> insert n+1 empty lines
20 .\" for manpage-specific macros, see man(7)
27 To preform the actual backup actions, backupninja processes each action configuration file in
28 /etc/backup.d according to the file's suffix.
31 run this file as a shell script.
33 backup action for rdiff-backup.
35 backup action for duplicity.
37 backup action for slow, incremental rsyncs of tens of thousands of maildirs.
39 backup action for safe MySQL dumps.
41 backup action for safe PostgreSQL dumps.
43 backup action for safe OpenLdap dumps.
45 backup action for general system reports and hardware information.
47 backup action for safe backups of subversion repositories.
49 backup action for safe backups of trac repositories.
51 backup action for burning backups to CD/DVD or creating ISOs.
54 These files must be owned by root and must not be world or group readable/writable. Support for additional configuration types can be added by dropping bash scripts with the name of the suffix into /usr/share/backupninja.
56 The configuration files are processed in alphabetical order. However, it is suggested that you name the config files in "sysvinit style."
59 10-disabled.ldap.disabled
64 Typically, you will put a '.rdiff' config file last, so that any database dumps you make are included in the filesystem backup. Action configurations which begin end with .disabled are skipped.
66 Example templates for the action configuration files can be found in /usr/share/doc/backupninja/examples. You can also use \fBninjahelper(1)\fP, a console based "wizard" for creating backup actions.
70 By default, each configuration file is processed everyday at 01:00 (1 AM). This can be changed by specifying the 'when' option in a backup action's config file or in the global configuration file.
73 when = sundays at 02:00
77 when = Tuesday at 05:00
80 These values for "when" are invalid:
85 A configuration file will be processed at the time(s) specified by the "when" option. If multiple "when" options are present, then they all apply. If two configurations files are scheduled to run in the same hour, then we fall back on the alphabetical ordering specified above. The "when" must occur before any sections in the action configuration file.
89 The file format of the action configuration files is "ini style." Sections are created by using square bracket. Long lines are connected with a backslash. For example:
98 i will not have a pear.
103 .BR backupninja.conf (5),
106 BACKUPNINJA was written by the riseup.net collective.