I did change the fileset to add an exclude in between. Would that cause all
the previously backed-up files to be backed up again? If so, I suppose I
should just delete the original job, and re-run the full backup. Seems
silly, though, to have it run a full backup just because an exclusion was
added.
Would it be possible to pull the excluded file from the first backup, and
then get an incremental? Just curious...
On Mar 30, 2009 5:09pm, John Drescher <dresche...@gmail.com> wrote:
2009/3/30 Justin Williams rjustinwilli...@gmail.com>:
> I am currently testing an incremental backup, and have it disabled. I
ran
> the backup and got a full backup, as expected, having not run it before.
> I then ran it again, and got that no full or suitable backup was found,
and
> that another full backup would be run.
>
> Is this caused by the backup being presently disabled? Or is there some
> other cause to this?
Did you change with the fileset or job definition between backups?
John
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
