Lloyd,
[Before I hit send, and looking back at your original message, I am not
sure if you can accomplish this. The docs say "Note, you define only a
single Job to do the Full, Differential, and Incremental backups since the
different backup levels are tied together by a unique Job name." here:
Jonathan,
I appreciate the suggestion. As it happens, we're not using different
devices. We're using file-based storage, and haven't ever seen the need
to be careful to keep them in different pools, etc.
Also, I'm slightly confused by your idea. If I'm understanding you
right, this wouldn't
On 6/17/19 12:15 PM, Kern Sibbald wrote:
> Hello Phil,
>
> I vaguely remember seeing some code a programmer changed that eliminated
> the "old" kludge to allow Solaris to run multiple threads. The comment
> I saw was that this was no longer needed on newer Solaris machines.
> Maybe the
Hello Phil,
I vaguely remember seeing some code a programmer changed that eliminated
the "old" kludge to allow Solaris to run multiple threads. The comment
I saw was that this was no longer needed on newer Solaris machines.
Maybe the programmer didn't realize that there are still lots of
Hello,
One other point about this. Semi-automatic detection of backing up files
multiple times could be done with the estimate bconsole command turning
on listing, then processing the output through sort and looking for
duplicates.
Perhaps an interesting "feature" might be to add another
Hello,
Yes, Bacula could become much smarter about this, but it requires two
things:
1. Bacula will require *significantly* more resources (CPU and memory)
to do such a backup.
2. You would need to find a programmer interested in writing the
necessary code -- it is not a monster project, but
