>>>>> On Mon, 16 Jul 2007 03:40:51 -0400, Ryan Novosielski said: > > Ralf Gross wrote: > > Troy Daniels schrieb: > >> Did /tmp/bacula-test/dir2 contain files created/modified before job 234? > > > > No I created /tmp/bacula-test/dir2 after job 234. > > > >> And if so, did Bacula back them up? > >> > >> Imagine this scenario: > >> > >> 1) /tmp/bacula-test/dir2 is created and files copied into it. > >> 2) Full Job 234 runs and does a full backup of /tmp/bacula-test/dir1 > >> 3) More files are added to /tmp/bacula-test/dir2 > >> 4) Fileset is updated to include /tmp/bacula-test/dir2 > >> 5) Incr Job 235 runs. > >> > >> Will job 235 only backup files created/modified since the last full > >> backup? Or is Bacula smart enough to recognise it's never backed this > >> directory up at all before and include all of it's contents. > > > > Ok, now I did the following: > > > > 1.) > > * created /tmp/bacula-test/dir3/foo3 > > * didn't change the fileset > > * run an incr backup > > > > Terminated Jobs: > > JobId Level Files Bytes Status Finished Name > > ======================================================================== > > 236 Incr 0 0 OK 12-Jul-07 11:11 xxxxx > > > > That's what I expected. > > > > 2.) > > * added /tmp/bacula-test/dir3/ to the fileset and reload the confg > > > > 237 Incr 0 0 OK 12-Jul-07 11:16 xxxxx > > > > The new files were not backed up! > > > > 3.) > > * created /tmp/bacula-test/dir5/foo5 > > * added /tmp/bacula-test/dir5/ to the fileset and reload the confg > > > > 238 Incr 2 0 OK 12-Jul-07 11:21 xxxxx > > > > > > It seems that files that were present at a previous backup are not > > backed up after adding the files to the fileset. > > So it looks like the final word on this is that it is OK to add new > directories to a fileset (or, a more common example in my case, new > filesystems) provided that they are really NEW directories. If I mkfs a > filesystem and add it to my backup, ignore fileset changes ought to be > OK. I suppose a fix could be that if you are newly adding a directory to > a backup and do not wish to do a full backup, you should touch all of > the files in that directory. The question is, what is the lightest touch > one can do that will cause these files to be added. > > I would love to hear an explanation about this problem, really... I know > that that is the way it is and that it might be a lot of work to change > it, but it seems to the casual observer that if a directory is currently > in the fileset (even if it was just added), and that directory contains > files, and Bacula does NOT contain any version of them in the catalog, > they should get backed up. Reliance upon filesystem timestamps is > probably not a great idea because timestamps can be played with. Are > they really necessary in a system that uses a catalog?
Bacula doesn't look at the files in the catalog when doing a Diff/Incr backup, only the date of the last backup compared to the mtime and ctime of each file. This is safe on unix, because (except for newly mounted filesystems) there is no API to set the ctime of a file. __Martin ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
