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 option to
estimate that would do exactly what I mentioned above then display all
the duplicates. Once a proper FileSet is made, there should really be
no need to go to the extra expense of looking for duplicates.
Best regards,
Kern
On 6/5/19 12:46 AM, Larry Rosenman wrote:
On 06/04/2019 5:25 pm, Chandler wrote:
Larry Rosenman wrote on 6/4/19 14:56:
Is there a way to have bacula see if it's backed up a path
already in this run and not do that?
What you could try is to do a restore job, then pick "list jobs where
a given file is saved" and you could get that listing.
Then in the director backup settings, you can update the Fileset
resource so it doesn't have duplicates and add "Ignore Fileset Changes
= yes" to prevent another Full backup from running, but ideally you
would run a new Full backup after updating the Fileset resource.
HTH,
I've already made that change, and the new Full's are running/have run.
I was just wondering if it would make sense for Bacula to become
smarter about this,
and be helpful and not duplicate the files.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
