Bug 689400

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Created attachment 499851 [details]
patch from Bacula bugs system

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
 - backup size was in some cases computed incorrectly 
Consequence
 - reported size of incremental backup could be wrong
Fix
 - computation of backup size is corrected
Result
 - reported size of incremental backup is correct

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,8 +1 @@
-Cause
+Prior to this update, the backup size was computed incorrectly under certain circumstances. As a consequence, the reported size of the incremental backup could have been wrong. The problem has been fixed by correcting the backup size computation process so that the size of the incremental backup is now reported correctly.- - backup size was in some cases computed incorrectly 
-Consequence
- - reported size of incremental backup could be wrong
-Fix
- - computation of backup size is corrected
-Result
- - reported size of incremental backup is correct

unfortunately, I'm unable to reproduce the error ... what are the exact conditions to trigger it?

- note that I've tried adding some options from http://bugs.bacula.org/view.php?id=1685 but it did not help

to be precise, I use:

FileSet {
  Name = "Full Set"
  Include {
    Options {
      signature = SHA1
      Accurate = mcs1
      basejob = pmugcs1
      checkfilechanges= yes
      compression = GZIP
      verify = pins1
    }
...

You need to run Full backup and then Incrementals.  Each incremental will be taking the same amount of space as Full according to bconsole (eg. in `list jobs`).

(In reply to comment #12)
> You need to run Full backup and then Incrementals.

that's what I did

> Each incremental will be taking the same amount of space as Full according
> to bconsole (eg. in `list jobs`).

when I add to the directory backed up half of the initial size before each incremental backup, it reports half the size of the first full backup for the incremental:

+-------+---------------+---------------------+------+-------+----------+----------+-----------+
| JobId | Name          | StartTime           | Type | Level | JobFiles | JobBytes | JobStatus |
+-------+---------------+---------------------+------+-------+----------+----------+-----------+
| 1     | BackupClient1 | 2011-08-26 06:49:32 | B    | F     | 101      | 103500   | T         |
| 2     | BackupClient1 | 2011-08-26 06:49:47 | B    | I     | 51       | 51750    | T         |
| 3     | BackupClient1 | 2011-08-26 06:49:57 | B    | I     | 51       | 51750    | T         |
| 4     | BackupClient1 | 2011-08-26 06:50:08 | B    | I     | 51       | 51750    | T         |
| 5     | BackupClient1 | 2011-08-26 06:50:18 | B    | I     | 51       | 51750    | T         |
| 6     | BackupClient1 | 2011-08-26 06:50:28 | B    | I     | 51       | 51750    | T         |
| 7     | BackupClient1 | 2011-08-26 06:50:39 | B    | I     | 51       | 51750    | T         |
| 8     | BackupClient1 | 2011-08-26 06:50:49 | B    | I     | 51       | 51750    | T         |
| 9     | BackupClient1 | 2011-08-26 06:50:59 | B    | I     | 51       | 51750    | T         |
| 10    | BackupClient1 | 2011-08-26 06:51:10 | B    | I     | 51       | 51750    | T         |
| 11    | BackupClient1 | 2011-08-26 06:51:20 | B    | I     | 51       | 51750    | T         |
+-------+---------------+---------------------+------+-------+----------+----------+-----------+

SanityOnly - I'm unable to reproduce the error

the patch is applied cleanly during the build and is reported (in upstream bugtracker) to fix the issue

the test /CoreOS/bacula/Sanity/backup-restore-sqlite which utilises incremental backups works with the new version (as well as with the old ...)

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1232.html