Hello, I wonder on the effects of attribute Ignore FileSet Changes of the FileSet resource.
I'm not sure what I have observed really corresponds to the doc neither to some comments made by Arno sometimes ago. >From http://www.bacula.org/dev-manual/Configuring_Director.html : "f this directive is set to yes, any changes you make to the FileSet Include or Exclude lists will be ignored and not cause Bacula to immediately perform a Full backup" I wondered about "how long" changes to Include or Exclude lists are ignored. Is it up to: 1. you set Ignore FileSet Changes to no ? 2. the next full backup ? My guess was: 1. Yes (sounds logical with the MD5 checksum of the FileSet) 2. I don't know. At this point, I was to send this mail, but finally decided to do some tests first. I've been very surprised by the results. Arno, on a list archive on nabble.com (Google indexing), you said (11.11.2005): "No. I don't know if I learnt this from the manual, some release notes, or The Hard Way(TM) but the fisrt job after adding "ignore fileset changes" will be a full one. The reason is that the fingerprint of the fileset, which is stored in the catalog, is changed with adding the option, and thus this fileset is considered a new one." I disagree. I don't observe this behavious. Set to "no" or "yes" the attribute does not mean a new FileSet checksum and the backups are still incremental. Maybe Bacula behavoir has changed ? The only changes that seem to imply a new checksum and so a Full backup next time , is changes on Files attribute, inside Include/Exclude sections. I added/removed/modified Wilddir attributes, onefs attrs, ... still incremental with the same FileSet checksum date and time. Another thing I was questionning myself was: if changes are ignore for sometimes, if I modify Files attributes, for example adding a directory, will it be ignore up to time T (T must be defined) or not ? I expected changes to be ignored. They are _not_. My sequence: Step 1 - Ignore FileSet Changes = no - File = /home/test/d1 - Requesting an incremental backup. It is actually incremental (the full done previously with the same setting) Step 2 - Ignore FileSet Changes = yes - File = /home/test/d1 - Requesting an incremental backup. Still observe an incremental. - No new FileSet checksum Step 3 - Ignore FileSet Changes = yes - File = /home/test/d2 (d1 and d2 have diffrent contents) - Requesting an incremental backup. Still observe an incremental. (d2 is backuped) - No new FileSet checksum Step 4 - Ignore FileSet Changes = no - File = /home/test/d2 - Requesting an incremental backup. Still observe an incremental. (d2 is backuped _again_) - New FileSet checksum I'm a little surprised by the results. I'm not sure this is the designed behavior by the developers. But I enjoy because this allows me to backup new directories or remove some with incremental backups. I just have to set Igore FileSet Changes to no before the next Full. Of course, as usual, I might have missed some points. However I think these results might interest some people and potentially Bacula developers. PS: for those who are still reading me at this line, thank you ;-) -- Baptiste MALGUY - IT Engineer SOLSOFT PGP Fingerprint: 2A90 B6D1 855F 1584 FE68 94AC CCD6 36D0 3DC7 DCB8 www.solsoft.com - phone: +33 1 47 15 04 00 - fax: +33 1 47 15 55 09 How secure networks are managed. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
