On Mon, May 17, 2010 at 10:21 AM, Uwe Schuerkamp
wrote:
> On Wed, May 12, 2010 at 12:59:53PM +0200, Uwe Schuerkamp wrote:
>> Hi folks,
>>
>> each time I cancel a backup job, the next job bound for that volume on
>> which the cancelled job ran Bacula marks the volume in error with a
>> "file count
On Wed, May 12, 2010 at 12:59:53PM +0200, Uwe Schuerkamp wrote:
> Hi folks,
>
> each time I cancel a backup job, the next job bound for that volume on
> which the cancelled job ran Bacula marks the volume in error with a
> "file count mismatch".
>
> I don't recall bad behaviour like this from pr
Hi folks,
each time I cancel a backup job, the next job bound for that volume on
which the cancelled job ran Bacula marks the volume in error with a
"file count mismatch".
I don't recall bad behaviour like this from previous versions (mainly
2.4 and 3.0.x), so is this a bug or a feature? Is it s
