On Thursday 10 July 2008 14:47:15 Dan Langille wrote:
> How does the above strategy cope with deleted files?  For example,
> foo.bar is
> included in the Full backup, but removed from disk before the next
> backup job.

This functionnality can work with or without accurate backup, (there is
no difference between them in catalog). If original backups are in accurate 
mode, deleted files will be take in account.

The vbackup startime will be set to the last backup found in catalog.

> How does this strategy deal with the above is:
> - foo.bar is not explicitly listed in the FileSet
> - foo.bar is explicity listed
>
> e.g. File = /usr
> versus File = /usr/foo.bar
>
> My thoughts: In the First case, the Vbackup job would not include
> foo.bar.  In the
> second case, it should.  In both cases, the file could be retrieved
> from the original
> Full backup.

In the second case, bacula will display an error during full/incr or diff 
backup. The vbackup doesn't use the fileset content to work.

> Critics who think it should always be included should not be using
> Vbackup.

vbackup of accurate backups should work quite well.

Bye

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users