[lbackup-discussion] Updates to backupscan.rb

[henri]

There is a new version of the backupscan.rb script available from the following URL : <http://www.lbackup.org/monitoring_multiple_backup_logs>

Typically, such an announcement would be posted to the LBackup announcements mailing list <http://lists.connect.homeunix.com/listinfo/lbackup-announce>.  However, in this case the discussion list has been used, in an effort to gain feed back regarding the significant changes to the way version 2.3 of the backupscan.rb script works. 

In particular, if a backup is in progress and this is the first run then, this will be reported as an error. As, such, a backup which has not had a successful backup (first run or otherwise within a specified time fram) will (with version 2.3 of backupscan.rb) be flagged as an error. This behaviour will most likely be updated in a future release (possibly by scanning for first run data). However, in this current release it is important to note this behaviour.

Also, new checks such as backup duration limits offer a range of improvements around reporting, which will most likely be of interest to many LBackup administrators.

Finally, it is also important to be aware that the latest backupscan.rb script will require LBackup_v0.9.8r5-alpha14 or later to be installed, as that release provides significant enhancements to both data within the logs and within the lock files, which provide version 2.3 of the backupscan.rb script with more accurate reporting of potential issues with a backup configuration.

Feedback regarding these most recent changes would be welcome; simply reply to this message. Should you prefer to keep your feed back off list, then simply contact Lucid Information Systems directly : http://www.lucidsystems.tk/contact/

If you have patches to improve the overheads associated with some of these new log scanning algorithms, then please submit these as pull requests on GitHub.

Thanks.
Henri