Home / server / Questions / 1057616
In Process
acropia
Asked: 2021-03-20 06:23:05 +0800 CST

Bareos (Bacula) FileSet not updated on change/reload/restart

  • 772

Problem

After building a Proof-of-Concept setup of Bareos, I can add and update various components like Clients, Devices, etc. But when modifying a FileSet, those changes are not reflected in the running Bareos config.

Details and research

PoC is built on Bareos 20.0.1, installed on a CentOS Linux 8.3 box. Till now all components, concepts and tasks are working as excepted. I can run backup and restore jobs succesfully.

When running bconsole, show filesets the updated fileset is visible (so it is read from config).

When running bconsole, list filesets the previous original fileset is listed. None of my modifications (i.e. added exclusions) is reflected over here.

When running jobs for new clients or rerunning previous jobs, I see no diferrence in FileSets in logging and no effects of my modifications (fewer files due to added exclusions).

Details:

  • Config file location: /etc/bareos/bareos-dir.d/fileset/XX.conf
  • Config file ownership: bareos:bareos

What I've tried

I've tried to reload/restart Bareos in a few ways, with no difference:

  • bconsole, reload
  • systemctl restart bareos-dir
  • reboot server

Tried to educate myself by Bareos and Bacula official documentation of various versions, but couldn't find a specific part which describes this behaviour.

backup bacula bareos

1 Answers

  1. After testing different situations I've found a solution/workaround. I'm not exactly sure if the current behaviour is intended or bugging, because I can not find anything about it in documentation. And I'm not skilled enough to verify it in source code.

    Workaround

    1. Modify the FileSet config file (i.e. filesets/FileSet.conf)
    2. Mofidy at minimum a FileSet, Include, File-statement, even if that is not the change you wanted.
    3. Reload Bareos Director
    4. At the next related Job-execution, the new FileSet is added to the Bareos database

    The trick I now use with frequently updates on Exclusions (WildDir) is to add a dummy File-statment like: File = "/tmp/dummy-0001". And number that up on each update.

    • 0