On Friday 15 January 2010 14:42:06 Gavin McCullagh wrote: > Hi, > > On Fri, 15 Jan 2010, Silver Salonen wrote: > > > > I was taken by surprise recently when I added an exclude to a fileset and > > > triggered a full backup. I guess the rule is "any changes to the fileset > > > will trigger a full backup" but is that really necessary on an exclude? > > > > There's an option "Ignore Fileset Changes" for not triggering full backup on > > every change. > > That's great, thanks. The manual is a little unclear on the effect of this > though (except to point out that you lose guarantees). > > http://www.bacula.org/en/rel- manual/Configuring_Director.html#SECTION001470000000000000000 > > If, for example, I exclude "c:\pagefile.sys", will that exclusion be > completely ignored until the next scheduled full backup (ie will it keep > backing it up until then)?
No, the option means just that the next job of the fileset is not going to be forced to full. The effect of exclusion etc. is still there though. > If you're using accurate incremental backups and run a virtualfull, is that > equivalent to a full for these purposes, or does a real full backup have to > be run? I don't think VirtualFull backup uses fileset to see which files to check and which not to - I guess it just merges multiple backups. I'm not sure though. But if a file has been marked as deleted by an accurate incremental backup, it won't be included in VirtualFull. -- Silver ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
