Bareos Maintenance Releases 12.4.8 – 13.2.5 – 14.2.6

Die Entwickler der OpenSource Backuplösung Baroes, dem Fork von Bacula, hatten Mitte Dezember Maintenance Releases für den 1. Releasekandidaten der Version 12, dem 2. Releasekandidaten 13. und dem 3. Releasekandidaten 14, veröffentlicht.

Nachfolgend die Liste der Änderungen und Bugfixe

Bareos 1. Releasecandidate 12.4.8

12.4.8  is a pure maintenance release. It does not add new features, this is the last maintenance for version 12.4.x.

The release is handled by the ticket ​#392

Bugs fixed:

• #556: Fix Windows File Relocation
• #529: Makefile clean action for stored not removing .libs directory
• #469: Dir crashes if media.ScratchPoolId = NULL
• #424: Fix use of wrong variable for WeekOfMonth check in next hour.

Bareos 2. Releasecandidate 13.2.5

13.2.5 is a pure maintenance release. It does not add new features.

The release is handled by the ticket ​#416

Bugs fixed:

• Fix Windows File Relocation
  • #556: File Relocation does not work
• AllowCompression setting doesn’t work with LZ4/LZFast
  • #497: AllowCompression setting doesn’t work with LZ4/LZFast
• Dir crashes if media.ScratchPoolId = NULL
  • #469: Dir crashes if media.ScratchPoolId = NULL
• Fix a bareos-dir segmentation fault
  • #446: bareos-dir segfault
• Fix use of wrong variable for WeekOfMonth check in next hour.
  • #424: Scheduling select wrong run line in schedule.

Bareos 3. Releasecandidate 14.2.6

14.2.6 is a pure maintenance release. It does not add new features.

The release is handled by the ticket ​#474

• Fix random crashes on sd
  • The block variable was set to the dcr->block, but that can be altered in
    the call to dev->set_label_blocksize(dcr).
    When that happens, the code goes on with the wrong block.
    We removed the whole local variable as it makes no sense and is only
    referenced 3 times when calling empty_block()
    #414: Bareos storage daemon crashes during backups
    #483: bareos-sd crash during backup
    #522: storage daemon crashes ocassionally when starting a new job
    #552: SD crashes in -current
• Fix Windows File Relocation
  • #556: File Relocation does not work
• Fixes a fd crash when using a invalid bpipe config
• logrotate: use “su” keyword only if available
  • Newer version of logrotate (>= 3.7 or 3.8, depending on the distribution)
    the “su” directive is required.
    Unfortunally, older version do not know about this keyword.
    With this patch configure detects, if “su” is a valid keyword in a
    logrotate configuration file.
    #537: usage of too-new “su” in logrotate file
• make MSSQL Incremental Backups restorable to files
  • #515: MSSQL Incremental Backups not restorable to files
• Fix state file truncation when running bareos-dir -t
  • When bareos-dir -t is run (which is done from the systemd startup) we
    never read the state-file nor create a pid-file but in the
    terminate_dird() function we unconditionally write a new state-file
    which means we clobber its content.
    We now keep track of the test_config flag using a static global variable
    and don’t try updating the state-file nor removing the pid-file in
    terminate_dird() when we are in test_config mode.
    Also made the terminate_dird() and terminate_stored() static as they are
    not referenced from anywhere else anyway so lets not clobber the
    namespace with it.
    #499: Director state file gets truncated
• AllowCompression setting doesn’t work with LZ4/LZFast
  • #497: AllowCompression setting doesn’t work with LZ4/LZFast
• fix a problem with the generic python-fd plugin
  • Don’t call PyCheckFile()
    When we have a inactive python-fd instance in a Job e.g. no option or
    file plugin definition in the fileset we are still called as part of the
    Checkfile method which calls each plugin loaded. This gives problems as
    we try to lookup the entry point into a non-existing python script and
    as such we have no dictonary at all which means the lookup will
    dereference a null pointer.
    #473: Incremental backup failure
• Fix a bareos-dir segmentation fault
  • #446: bareos-dir segfault

Quelle: https://www.bareos.org/en/news/new-maintenance-releases-published-138.html