I had a bacula differential backup fail over the weekend due to a host
being down.  The next time backups ran, the host was scheduled for an
incremental.  I was expecting bacula to promote the incremental to a
differential.  It didn't -- it ran the backup as an incremental.  Can
anyone tell me why, and/or what I need to do so this won't happen?

The server with the director and sd is running bacula 2.4.4 under
Linux.  The client is running Windows, winbacula 2.4.4.

Here are relevant lines from list jobs:

| 506   | windowshost   | 2009-03-27 19:09:09 | B    | I     | 285      | 756351
| 510   | windowshost   | 2009-03-27 23:20:58 | B    | I     | 0        | 0     
| 517   | windowshost   | 2009-03-28 23:12:06 | B    | I     | 0        | 0     
| 524   | windowshost   | 2009-03-29 23:17:11 | B    | D     | 0        | 0     
| 531   | windowshost   | 2009-03-30 23:37:59 | B    | I     | 625      | 148620

[hostname changed to protect the guilty.]

At one point, I saw the status of the bad differential job as "other"
rather than a more normal failure mode.  Does this make sense?

I have since run a differential job manually on the host in question.
But I'd like to know how to prevent recurrences of this problem.

- Morty

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users