Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

backup.d(5) [debian man page]

BACKUP.D(5)							backupninja package						       BACKUP.D(5)

NAME
BACKUP.D - Action configuration files for backupninja(1). SYNOPSIS
/etc/backup.d/* DESCRIPTION
To preform the actual backup actions, backupninja processes each action configuration file in /etc/backup.d according to the file's suffix. .sh run this file as a shell script. .rdiff backup action for rdiff-backup. .dup backup action for duplicity. .maildir backup action for slow, incremental rsyncs of tens of thousands of maildirs. .mysql backup action for safe MySQL dumps. .pgsql backup action for safe PostgreSQL dumps. .sys backup action for general system reports and hardware information. .svn backup action for safe backups of subversion repositories. .trac backup action for safe backups of trac repositories. .makecd backup action for burning backups to CD/DVD or creating ISOs. 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. The configuration files are processed in alphabetical order. However, it is suggested that you name the config files in "sysvinit style." For example: 10-local.pgsql.disabled 15-runthisfirst.sh 20-runthisnext.mysql 90-runthislast.rdiff Typically, you will put a '.rdiff' config file last, so that any database dumps you make are included in the filesystem backup. Action con- figurations which end with .disabled are skipped. Example templates for the action configuration files can be found in /usr/share/doc/backupninja/examples. You can also use ninjahelper(1), a console based "wizard" for creating backup actions. SCHEDULING
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. Special value 'manual' will disable scheduling for the backup action. It is pos- sible to run the backup action manually by invoking ninjahelper(1) with --run command line argument. For example: when = sundays at 02:00 when = 30th at 22 when = 30 at 22:00 when = everyday at 01 when = Tuesday at 05:00 when = hourly when = manual These values for "when" are invalid: when = tuesday at 2am when = tuesday at 2 when = tues at 02 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. FILE FORMAT
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: # this is a comment [fishes] fish = red fish = blue [fruit] apple = yes pear = no thanks i will not have a pear. SEE ALSO
backupninja(1), ninjahelper(1), backupninja.conf(5), AUTHOR
BACKUPNINJA was written by the riseup.net collective. riseup October 10, 2005 BACKUP.D(5)

Check Out this Related Man Page

BACKUPNINJA.CONF(5)						backupninja package					       BACKUPNINJA.CONF(5)

NAME
BACKUPNINJA.CONF - Configuration file(s) for backupninja (1). SYNOPSIS
/etc/backupninja.conf DESCRIPTION
backupninja.conf is the general configuration file. In this file you can set the log level and change the default directory locations. You can force a different general configuration file with "backupninja -f /path/to/conf". OPTIONS
loglevel How verbose to make the logs. 5 = Debugging messages 4 = Informational messages 3 = Warnings 2 = Errors 1 = Fatal errors reportemail Send a summary of the backup status to this email address reportsuccess If set to 'yes', a report email will be generated even if all modules reported success. reportwarning If set to 'yes', a report email will be generated even if there was no error. logfile The path of the logfile. configdirectory The directory where all the backup action configuration files live. scriptdirectory Where backupninja handler scripts are found usecolors If set to 'yes', use colors in the log file and debug output. when When to process each configuration file. The value used here will be applied for each configuration file. It is possibile to over- ride this "when" in each each configuration file, see also section "Scheduling" in backup.d(5). For example: when = sundays at 02:00 when = 30th at 22 when = 30 at 22:00 when = everyday at 01 <-- the default when = Tuesday at 05:00 These values for 'when' are equivalent: when = tuesday at 05:30 when = TUESDAYS at 05 These values for 'when' are invalid: when = tuesday at 2am when = tuesday at 2 when = tues at 02 vservers If you are using Linux-Vservers (http://linux-vserver.org), there are some special capabilities that different handlers have to make vserver backups easier. See the example configuration files for each handler to configure the vserver specific variables. DEFAULTS
loglevel = 4 reportemail = root reportsuccess = yes reportwarning = yes logfile = /var/log/backupninja.log configdirectory = /etc/backup.d scriptdirectory = /usr/share/backupninja usecolors = yes when = everyday at 01:00 vservers = no SEE ALSO
backupninja(1), ninjahelper(1), backup.d(5), AUTHOR
BACKUPNINJA was written by the riseup.net collective. riseup November 19, 2005 BACKUPNINJA.CONF(5)
Man Page