From: Dan L. <da...@la...> - 2008-08-30 15:47:57
|
Timo Neuvonen wrote: >>> I have a couple of users which sporadically edit video files. >>> >>> These files can take several hundred megabytes and are also subject to >>> backup. >>> >>> The thing is, users often move these files, i.e. from directory A to >>> directory B. And copy to directory C two days later. The next day, they >>> change files name from movie_a.avi to new_commercial.avi. >>> >>> All these file renames/copying/moving make a big problem for our current >>> backup setup - the files are transferred again and again over slow >>> Internet, although files didn't change and their checksums are still the >>> same. >>> >>> >>> Can Bacula deal with file renames, copying (their time stamp can >>> differ), moving etc.? >> Bacula will backup everything in a Full backup. >> >> For the next Incremental or Differential, it uses mtime. That is, the >> last time the file was modified. If the mtime has not changed, the file >> will not be backed up, regardless of name. >> >> So, for your example: if the file is copied, mtime [usually] changes. >> So it will be included in the next inc/diff backup. Renaming a file >> does not change mtime. Therefore the renamed file will not be included >> in the next inc/diff backup. >> > Just out of curiosity: what information Bacula uses to recognize a renamed > file, in addition to mtime? I am not sure what you mean by "recognize". Bacula does do anything like that (here I am giving you an answer based on not knowing what you mean). > Or is mtime guaranteed (in all filesystems) to > be unique, so there couldn't be another file with the same mtime? mtime is not unique. Multiple files can have the same mtime. |