News for hackers. Stuff that matters.

A comment on BorgBackup, Deduplicating archiver with compression and encryption. Parent comment

Re:BorgBackup, Deduplicating archiver with compression and e... by aborsy on Wednesday December 28, 2022 @01:25AM (#34158078)
These backup software are all incremental, work similarly and take similar times (difference is in details). If you lost locally cached metadata files keeping information on what has changed, they all have to scan the whole source again.
[ Parent | on HN ]
Re:BorgBackup, Deduplicating archiver with compression and e... by nine_k on Wednesday December 28, 2022 @03:47AM (#34158941)
Scanning 4TB for a week? It should not take as long even if you use magnetic tapes and change them manually.

I suppose the latency of the remote server was too high.

[ Parent | on HN ]
Re:BorgBackup, Deduplicating archiver with compression and e... by noAnswer on Wednesday December 28, 2022 @10:41AM (#34162068)
> work similarly and take similar times

Except that I tested them and they didn't. I hadn't "lost locally cached metadata". And it didn't just scan all the source files again, it re-transferred them over the network. All 4TB of it! That's why it took so long. (At that time the sever was still local, because I wanted to make the initial run not over the Internet. So there wasn't even added latency.)

I'm sure it was a bug, maybe even in combination with OpenBSD, which moste likely is fixed now. As I said it was years ago. I compared and was more happy with borg. Which stood the test of time and saved my ass multiple times.

[ Parent | on HN ]
Re:BorgBackup, Deduplicating archiver with compression and e... by bttger on Saturday December 31, 2022 @06:25AM (#34195464)
This probably wasn't a bug. I experienced the same last week but it was because I ran the backup command from a different directory. I've created a note saying:

`restic backup -v -r <location>/<repo_name> <source_dir>`

first `cd` to the parent directory of the `source_dir` to avoid too many nested directories in the repository and conflicts in the mounting point path (so that the file change detection of restic works when mounting the drive to be backed up at another point)

[ Parent | on HN ]