I started making regular backups to Hubic. It worked well until a few days ago, when on another machine, getting the snapshot list would send resting in a big loop of read errors.
I then created an account on Wasabi, used rclone to copy data and resumed making backups.
On the good side, Wasabi seems to be working more correctly than Hubic and I didn’t get a network error yet.
I’m using the word correctly because rclone can list files it can’t read. So I do expect and accept data loss.
I could start a new repo, but…
- I have 200 GB already uploaded, so making new backups now should be faster.
- Failures also happen in real life, so it’s an opportunity to see how restic reacts when thigs go bad.
I would like to be able to have the check command succeed, by trimming tress that are incomplete or link to incomplete files.
Result of restic check:
(...) error for tree bc2e8dc5: tree bc2e8dc5: file "IUPnPCDSAdapter.cpp" blob 0 size could not be found tree bc2e8dc5: file "IUPnPCDSAdapter.cpp": metadata size (1600) and sum of blob sizes (0) do not match tree bc2e8dc5: file "UPnPDMS.cpp" blob 0 size could not be found tree bc2e8dc5: file "UPnPDMS.cpp": metadata size (3773) and sum of blob sizes (0) do not match tree bc2e8dc5, blob 8438c98b: not found in index tree bc2e8dc5, blob 789ff404: not found in index Fatal: repository contains errors
My history so far:
restic rebuild-index restic prune restic check --check-unused --read-data restic check restic rebuild-index