Le 20/11/2018 à 18:39, Craig Barratt via BackupPC-users a écrit :
> Steve,
>
> You are exactly right - BackupPC's storage granularity is whole
> files. So, in the worst case, a single byte change to a file that is
> a unique will result in a new file in the pool. Rsync will only
> transfer the de
Thanks for confirming, Craig. There are lots of approaches that I could
use to reduce the duplication, but they would all add complexity
needlessly if BackupPC was already storing just deltas at a high
granularity (and I completely understand the decision not to do so).
I'm currently looking a
Steve,
You are exactly right - BackupPC's storage granularity is whole files. So,
in the worst case, a single byte change to a file that is a unique will
result in a new file in the pool. Rsync will only transfer the deltas, but
the full file gets rebuilt on the server.
Before I did the 4.x rew
Thanks. Yes, I had seen that in the docs but I got the impression that
the deltas referred to there were at the granularity of whole files. For
example, let's say backup 1 contains files A, B and C. If B is then
modified then, during the next backup rsync might only /transfer/ the
deltas needed
Hi Steve,
It looks like they are stored using reverse deltas. Maybe you’ve already seen
this from the V4.0 documentation:
* Backups are stored as "reverse deltas" - the most recent backup is always
filled and older backups are reconstituted by merging all the deltas starting
with the neare
