On 2020-05-23 23:47, backu...@kosowsky.org wrote:
Regarding your comment:
However, I don't think it makes sense to
"fix" it, since a backup shouldn't add metadata that changes each time
you
backup some data that hasn't changed.
Actually, the whole point of --ignore-dir-times is that the
Regarding your comment:
> However, I don't think it makes sense to
> "fix" it, since a backup shouldn't add metadata that changes each time you
> backup some data that hasn't changed.
Actually, the whole point of --ignore-dir-times is that the dir mod
time is not changed each time you rsync.
Thanks for the updates. Yes, rsync's included zlib isn't compatible with
system zlib. However, since you are not using the -z option, I don't think
that's the issue.
Can you try rsync-bpc 3.1.2.1? It has more testing than 3.1.3.beta0.
Craig
On Sun, May 24, 2020 at 7:43 PM wrote:
>
Upgrading to the latest rsync-bpc 3.1.3 fixed the problem with
specials.
And restores all seemed to work last night, until I tried dumps today.
Now all my scheduled backups fail with error message:
rsync error: error in rsync protocol data stream (code 12) at io.c(226)
[Receiver=3.1.3.beta0]
Jeff,
I did set the policy to permissive. If I get some time I'll try again.
Craig
On Sat, May 23, 2020 at 10:30 PM wrote:
> Thanks Craig.
> The --specials now works (and I agree with both you and Michael that
> it is not useful... but it validates that the restore is 'perfect' as
> far as
