ThomasWaldmann

6 ms·

31.
by ThomasWaldmann 5y ago
Yeah, that's an issue which can be avoided by using 1 repo per client. There are some ideas on the issue tracker for fixing this long term (like random nonces, session keys, ...), but that stuff will have to wait until after borg 1.2 (
32.
by ThomasWaldmann 5y ago
borg maintainer here: Yeah, restic is a great backup tool also. OTOH it is a pity the we could not join forces (Python vs. Go and also some other differences), but otoh it means more choice for everybody wanting a nice deduplicating backup
33.
by ThomasWaldmann 5y ago
Just wanted to point to the FAQ section inside the borg docs. https://borgbackup.readthedocs.io/en/stable/faq.html#can-i-c...
34.
by ThomasWaldmann 5y ago
1. as borg always does FULL backups, it needs to access all files' metadata anyway. that together with borg's "files cache" enables borg to quickly detect and back up unchanged files. the created archive always contains
35.
by ThomasWaldmann 5y ago
I don't know exdupe, but from a quick glance at their homepage it looks like a full + differential style backup. With borg, every backup is logically a full backup (it just is faster due to deduplication). Much easier and less time con
36.
by ThomasWaldmann 5y ago
borg does either use a directory as repo (no matter whether local or mounted via network fs) or works client/server via pipes that are usually over ssh (in that case, it needs a remote borg process to talk to). instead of ssh, one coul
37.
by ThomasWaldmann 5y ago
borg maintainer here: attic should not be on the list, it is unmaintained since 2015. borg came into life as a fork of attic for related reasons, so it should be borg (Python+Cython+C).
38.
by ThomasWaldmann 5y ago
Maybe have a look at borgbackup docs to use the same terminology, otherwise it might get confusing. When you create a backup ARCHIVE in a borg REPOSITORY, the archive contains all input files you gave to borg. Each archive has a name and us