Tomasz Chmielewski wrote:
> Dan Langille schrieb:
> 
> (...)
> 
>> Bacula will backup everything in a Full backup.
> 
> Hmm, does "Bacula will backup everything in a Full backup" mean "it will 
> transfer *everything* over network, even if the same files in the same 
> location were in the previous full backup?

Yes.

> 
> 
>> 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.
>>
>> Referring to another post of yours: the "accurate restore" mentioned by 
>> Frank will still continue to backup files that are identical.  That is, 
>> if you have 10 files that contain identical content, all ten will be 
>> backed up.
> 
> Yes, I also expect to find all these files in backup.
> The problem is, I don't want to transfer all these files again and again 
> if the same file is already in the pool.

A full backup, by definition, backs up all files.

-- 
Dan Langille

BSDCan - The Technical BSD Conference : http://www.bsdcan.org/
PGCon  - The PostgreSQL Conference:     http://www.pgcon.org/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users