Stop doing catalog backups
authorPeter Palfrader <peter@palfrader.org>
Tue, 24 Sep 2019 09:44:14 +0000 (11:44 +0200)
committerPeter Palfrader <peter@palfrader.org>
Tue, 24 Sep 2019 09:44:14 +0000 (11:44 +0200)
commitfc79f92600028a6dea9d8dc67c78247a0cd2d62f
treef4ad6b5c4ace62c751d7308fe59e907d5c3788d4
parent6bd8475576cb562efe04ed9b4cc406d729055413
Stop doing catalog backups

The bacula catalog backup job is this special snowflake that's unlike
all the other jobs.  It only backups one file,
/var/lib/bacula/bacula.sql.gz, that gets created in a RunBeforeJob
and deleted in a RunAfterJob.

We already have a well-thought out and more generic method to backup
databases, and we should use just that.

The RunBefore/After setup makes sense as a default when you don't have
that, but we do.
modules/bacula/manifests/storage.pp
modules/bacula/templates/bacula-dir.conf.erb
modules/bacula/templates/bacula-sd.conf.erb