Re: [rdiff-backup-users] State of the rdiff-backup project

[Claus-Justus Heine]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 14.08.2015 um 19:12 schrieb Robert Nichols:
> On 08/13/2015 02:16 PM, Claus-Justus Heine wrote:
> increments.  In large part it's due to use of the filesystem as a
> database, with bits of information scattered in file names in the
> increments directory and various metadata files. You're not going to
> change that without a major rewrite.

Mmmh. Still I think it would be a good idea to first understand what's
going on there.

> I suppose one solution to the regression issue is to store the archive
> in a filesystem or LVM volume that supports snapshots.  Rather than le
t
> rdiff-backup do the regression, stop it and restore the snapshot. I
> suspect the penalty in space (transient, until the snapshot is deleted
)
> and performance for the backup would be serious. And that still leaves
> the issue of regressing more than the last level.

Well, that would be a nice solution. I do not understand this "more than
one level". If we are only talking about a failed backup, then one level
is the worst thing which can happen: last backup succeeded, this backup
fails, discard the file-system snapshot, fix the underlying error and re
try.

> Like you, I'm no Python guy. Every time I try to study it, I end up as
 a
> lump in a snake's belly. I think it's because there are some things
> about the language that I hate (starting with the use of whitespace as
 a
> syntax element) and the incompatibility of major versions. And then
> there is the tendency of Python programmers to believe that stack
> backtraces are an acceptable substitute for meaningful error messages.
> It all leaves a bad taste that I just can't get around.

Ok, so: for myself my largest programming experience is in C and C++,
more or less. Still: Python is widely used, it seems to be convenient
for beginners, and: rdiff-backup is written in Python, no need to start
something new. Seemingly, there is no real pressure to migrate to v3 ...

Concerning the Python language personally I rather feel the lack of
internal functions (private, protected etc.). However, so what. C++ is
really really by far (maybe farest) imperfect and still carries tons of
historical ballast.

Many thanks for the feedback, best,

Claus

- -- 
Claus-Justus Heine                      address@hidden

http://www.claus-justus-heine.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVzjveAAoJEF8rbXubOwvKnAcQAKzJTyTo/eUq2jnGuRkQbAAE
jbXukFwSbYukTpGmLC6ibdrRJd3AIuXQg0DnOPBV9DhxM/bBPBoYqXfUZ5GQT43Y
f4JIIiHk/cBrh41IhQIEWGJc12v/DnSaaToNIAR/yYPEb0o3yimVnMeXD10hPVAD
jm/JRhajcUIHkBJesk7YcJRhdko/aOAoNMcNSh+goM51EQNu6CF2zrvjvJzVriFy
BDGe/EyQaWDniynJ7OFj1P67IL3DJ1MkQETdr4Ehu6qUGOFRBfF5myKQondT+l+K
oD0N/O/xlu8JqFtFR2XNJQC8JNg6wEfOJOdPVwA1Xh0qeCOLcwSFKJGjPuGQ/O/5
8I7ThQwK1B4693HbiUtMuiTPuN8ogMW/J4CFlgPJEUQDI5b3kWZBQvbaihZHmbq0
RORw8eFAmTaSrnmJ4WYwPu6R51+BfvvikMV9b0JnSOAPPZZV+LfyTieQDQILR6Qk
D4/4LHQnIjHX4izPRFvQnb5dsh55zEgwbI9+w65siVRIgNPcHVYD6AIYSJ+8QHCf
Ebu2mL96LMKQMcvVt4CiRVp7W0AY16O66chkw1taHTKxfYl1j/v2MFisJCt0nZrw
pqU3NZR781EXH5Z8wiWr/wbIgUweFol1Z0lSxu5oMO4XD0IwglmIRIUESNftApOL
j4o9tKFYdxIrcxuZbh80
=ALgH
-----END PGP SIGNATURE-----