... | ... | @@ -544,6 +544,29 @@ Will list all the jobs ran on `corsicum` that are still valid |
|
|
reason, but at least the `corsicum` jobs will be shown last so they
|
|
|
can be found more easily.
|
|
|
|
|
|
## Excluding files from backups
|
|
|
|
|
|
Bacula has a list of files excluded from backups, mostly things like
|
|
|
syntetic file systems (`/dev`, `/proc`, etc), cached files
|
|
|
(e.g. `/var/cache/apt`), and so on.
|
|
|
|
|
|
Other files or directories can be excluded in two ways:
|
|
|
|
|
|
1. drop a `.nobackup` file in a directory to exclude the entire
|
|
|
directory (and subdirectories)
|
|
|
|
|
|
2. add the file(s) to the `/etc/bacula/local-exclude` configuration
|
|
|
file (lines that start with `#` are comments, one file per line)
|
|
|
|
|
|
That configuration is made in the
|
|
|
`modules/bacula/templates/bacula-dir.conf.erb` Puppet template,
|
|
|
deployed in `/etc/bacula/bacula-dir.conf` on the director. The files
|
|
|
to be *included* in the backups are basically "any mounted filesystem
|
|
|
that is not a bind mount and one of `ext{2,3,4}`, `xfs` or
|
|
|
`jfs`". *That* logic is defined in the
|
|
|
`modules/bacula/files/bacula-backup-dirs` Puppet file, deployed in
|
|
|
`/usr/local/sbin/bacula-backup-dirs` on backup clients.
|
|
|
|
|
|
## Pager playbook
|
|
|
|
|
|
Hint: see also the [howto/postgresql](howto/postgresql) documentation for the backup
|
... | ... | |