Am 27.06.2014 16:25, schrieb John Drescher:
>> I receive this error info:
>> "Cannot automatically recycle current volume, as it still contains
>> unpruned data or the Volume Retention time has not expired"
>>
>> I don't get this, with the directives "AutoPrune" and "Volume Retention"
>> this shoul
Kern> Yes, it is clear that one can do read-only tests that do not destroy
Kern> data. However, in this case, it seems to me more useful to do
Kern> read/write (it is actually write/read) tests as it appears that the
Kern> problem is more likely in the write ...
Absolutely. And hopefully, this
Hello,
2014-06-30 15:23 GMT+02:00 Bill Arlofski :
> Hi list, Hi Kern,
>
> Recently, I have been noticing that jobs I have temporarily disabled at the
> bconsole prompt had been 'randomly' showing back up in the list of
> scheduled
> nightly jobs.
>
> I just noticed that this happened again to me
Hi list, Hi Kern,
Recently, I have been noticing that jobs I have temporarily disabled at the
bconsole prompt had been 'randomly' showing back up in the list of scheduled
nightly jobs.
I just noticed that this happened again to me this morning, and determined
that I had just modified a config fil
On 6/29/2014 11:07 AM, Kern Sibbald wrote:
> It is also curious
> to say that Burp "started out" as a fork of Bacula. Is there a point
> where a fork stops being a fork?
It is a philosophical question, of course, but I would say when it is no
longer easily recognizable as a fork. It will always
I have seen this before with both disk and tape media, where a backup
job with no errors cannot later be restored due to i/o errors. The
simple answer is that media can fail, even when offline, which is one of
the reasons we make more than one backup.
It is possible, if cumbersome and expensive
On 06/30/2014 06:42 AM, keel...@spamcop.net wrote:
> Quoting Kern Sibbald :
>> Hello Graham,
>>
>> Thanks for your "Full disclosure".
>>
>> To answer your question: a *well* tuned Bacula community Director can
>> probably handle between 1000-1500 "normal" size jobs per 12 hour backup
>> period. A
Hello,
Yes, it is clear that one can do read-only tests that do not destroy
data. However, in this case, it seems to me more useful to do
read/write (it is actually write/read) tests as it appears that the
problem is more likely in the write ...
I have never heard of a non-destructive read/writ
