For the record, this is one of a handful of reasons that I switched from
smb to rsync. The others:
2) smbclient has a hard coded timeout value, which can mean dying on large
files
3) rsync can be make to take advantage of VSS to back up open files (which
I've detailed.)
>> I understand that thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alessio Oss wrote:
>>> Why? Other people have the same problem?
>> Why? Because you're using SMB, which is using time/date stamps to
>> determine what goes in the incremental backup, and the files haven't
>> changed.
>
> Why not?
> They are the s
>>
>> Why? Other people have the same problem?
>>
>> tnX
>
> Why? Because you're using SMB, which is using time/date stamps to
> determine what goes in the incremental backup, and the files haven't
> changed.
Why not?
They are the same but are on a different position and despite i think
that
> Situation:
(clip)
>
> If, after making this change, I would make an incremental backup, host I
> was faced with this situation CORRUPT:
(clip)
> Situation is OK, both with version 3.0.0 and 3.1.0, when I do a full
> backup.
>
> With both versions, starting from the situation CORRUPT, if I edi