Package: bacula-common
Version: 1.38.9-10
Severity: wishlist
Hi,
I think, it would be useful, if the default config
bacula-dir.conf would split off the parts for Catelog
backup.
The idea is as follows:
1) Move the following parts of bacula-dir.conf out into a
new /etc/bacula/backup-catalog.conf:
- Job { Name = "BackupCatalog" ... }
- Schedule { Name = "WeeklyCycleAfterBackup" ... }
- FileSet { Name = "Catalog" ... }
2) possibly rename the schedule to
CatalogWeeklyCycleAfterBackup to make it more unique.
3) The resulting file has no machine name or password in
it. It is easier to upgrade (if for example the FileSet
has to change)
It can be managed as a conffile or using ucf.
4) Add "@/etc/bacula/backup-catalog.conf" in
bacula-dir.conf.
Migration options:
a) Install the new backup-catalog.conf and don't care
further.
b) Do (a) and tell people to remove their old stuff from
bacula-dir.conf and add in the @/etc/... in
README.Debian
c) do (b) and check for missing @/etc/... and warn using
debconf.
d) Do (c) and offer to auto-update (probably very hard and
errorsome job).
Benefits:
* Better upgrade path for the case of other Catalog backup
scripts.
* The more useful parts (Catalog backup) the the more
examplish parts (Fileset "Full Set") get better
seperated.
Issues remaining:
- The RunBeforeJob command has the db user and password in
it:
- It's wrong anyway, like it is.
- One should not have passwords on the commandline, where
they're visible to other users using "ps"
I hope you consider this idea.
Elrond
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
