borgbackup / borgbackup/borg

idea: healing backup

Open
#3,904 2 comments 3 reactions 0 assignees View on GitHub
cmd: check cmd: create
Dominant language
Python
Stars
13.7k
Forks
875
Avg merge
11h 15m
Merged PRs (30d)
192

Description

On IRC, a anon borg user had an interesting idea:

There could be a combination of backup and integrity check: if the backup run detects a duplicate chunk, it would read the chunk from the repo and check its integrity. If integrity check fails, it would delete the chunk from the repo and store the current data (of same id_hash) into the repo, healing the defect.

Issues with that:
- of course that this is super-slow compared to how borg normally operates as it would read the whole backup volume from the repo (it usually only transfers new data to the repo)
- a simple implementation might check the same chunk multiple times if it appears in input data multiple times.
- when using the files cache, data of unchanged files is usually NOT read from disk, but could be in case of an integrity error in the repo

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.