As a new user to Restic I have had mixed experience. Most repo’s have backed up okay, but one repo has always produced errors. I started out using Borg and got errors on a similar backup process, which made me then consider “restic”. I have found restic to be faster on the first and subsequent backup operations over TB of data.
Most of the files are video mkv files. Source and repo drives are local to the PC.
Version: | debug enabled | restic 0.9.6 (v0.9.6-349-gfe69b830) compiled with go1.15 on linux/amd64
I disable clamav-daemon.service
After running
/usr/bin/restic $RESTIC_OPTIONS \
--files-from "$INCLUDEFILE" \
--exclude-file "$EXCLUDEFILE" \
-r "${REPO}" \
backup "${SOURCE[i]}" >>"${LOGBACKUP}" 2>&1
and then forget/prune:
/usr/bin/restic "$GLOBAL_OPTIONS" forget \
--keep-daily 7 \
--keep-weekly 5 \
--keep-monthly 6 \
--keep-yearly 10 \
--keep-last 7 \
--prune \
-r "${REPO}" >>"${LOGFORGET}" 2>&1
then a basic check:
/usr/bin/restic "$CHECK_OPTIONS" \
check -r "${REPO}" >>"${LOGCHECK}" 2>&1
I get no errors.
debug enabled
using temporary cache in /tmp/restic-check-cache-682081467
created new cache in /tmp/restic-check-cache-682081467
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
no errors were found
However, after running another check with --read-data enabled I start to get errors
debug enabled
using temporary cache in /tmp/restic-check-cache-921366440
created new cache in /tmp/restic-check-cache-921366440
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
read all data
Pack ID does not match, want eb297dda, got adeaa6db
pack cd462026 contains 1 errors: [blob 3: ciphertext verification failed]
pack 5b04aa31 contains 1 errors: [blob 0: ciphertext verification failed]
I have run $ memtest64+
without issues and smartctl output shows no issues for the source or repo drives, which are both local to the PC.
I have run a
$ diff dir1 dir2
between the mounted repo snapshot directory and the source directory and got one file that was apparently different. Copied that file back to my disk and did a $ cmp file1 file2
with no difference showing.
I’m at a loss to get this working error free.
Then I took the sub-directory that contained the problem file mentioned above and created a smaller backup of that directory into a new repository. The backup completed without errors. I then did a check on that repo with --read-data
enabled. No errors were found for this process.
I also have this issue occurring for other drives for their backup to separate repositories when running $ check --read-data
It is hard not to think a bug in restic might be the issue. It is as if what it reads before saving is not what it actually saves so a checksum error occurs. I see it is not reached v1 yet so I guess it is still under heavy development. I’ve noticed other issues that I’ll raise in another post.
Running $ check --read data
is a long process when the drives have TB of data (~30+ hrs). So it is difficult to have confidence yet while this occurs as it takes at least 2+ days to realise there is an error.