>>>>> On Mon, 18 Jul 2005 21:31:56 +0200, Kern Sibbald <[EMAIL PROTECTED]> said:
Kern> On Monday 18 July 2005 19:32, Martin Simmons wrote: >> >>>>> On Fri, 15 Jul 2005 23:46:00 +0200, Arno Lehmann <[EMAIL PROTECTED]> >> >>>>> said: >> Arno> Volker Sauer wrote: >> >> On Fr, 15 Jul 2005, Mario Ohnewald wrote: >> >>> In my eyes this is a huge "bug". >> >>> >> >>> Lets says you have a big home directory with a couple of projects and >> >>> sourcecode files in there, and you reorganize the folder structure >> >>> and you move some files and folders around. >> >>> >> >>> All this then would NOT be included in a backup! >> >>> What's the point of a backup then? >> >> >> >> In this case you should submit a bug in the bug database at >> >> bacula.org. >> Arno> Indeed. Arno> According to bacula's manual, Director configuration, Jobs, Job >> Level Arno> Incremental: >> Arno> The File daemon (Client) decides which files to backup for an Arno> Incremental backup by comparing start time of the prior Job (Full, Arno> Differential, or Incremental) against the time each file was last Arno> ``modified'' (st_mtime) and the time its attributes were last Arno> ``changed''(st_ctime). If the file was modified or its attributes Arno> changed on or after this start time, it will then be backed up. >> Arno> So, a mv'ed file should be backed up: Arno> # ls >> datetest Arno> # ls -l datetest Arno> -rw-r--r-- 1 root root 944 Jul 15 23:20 datetest Arno> # ls -lc datetest Arno> -rw-r--r-- 1 root root 944 Jul 15 23:20 datetest Arno> # sleep 60; mv datetest testdate Arno> # ls -lc testdate Arno> -rw-r--r-- 1 root root 944 Jul 15 23:21 testdate Arno> # ls -l testdate Arno> -rw-r--r-- 1 root root 944 Jul 15 23:20 testdate >> Arno> So, at least o my linux box the ctime is modified by mv'ing a file >> - Arno> which is correct concerning POSIX etc. standards, I believe. >> Arno> Accordingly, bacula should back up this file. >> >> Correct, but if you move a directory then the files within it do not change >> ctime or mtime and hence will not be backed up. E.g. >> >> # mkdir -p test1/inner test2 >> # ls >> test1/inner/datetest >> # ls -l test1/inner/datetest >> # ls -lc test1/inner/datetest >> # sleep 60; mv test1/inner test2 >> # ls -lc test2/inner/datetest >> >> In fact, they probably shouldn't be backed up -- it is another variant of >> the problem with incr/diff restore not restoring renamed things correctly. Kern> I would word it differently, because as far as I know restore always restores Kern> correctly what is backed up. Kern> It is another variant of the fact that Bacula uses timestamps for diff/inc Kern> backups so doesn't know when files are deleted, and if files are added with Kern> old timestamps, it doesn't know they are added -- until you do a full save. Well, yes, you can say that it is a bug in backup too because it doesn't save enough information for restore to work :-) __Martin ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
