I’m using restic 0.17.3 compiled with go1.23.3 on darwin/amd64.
I’ve been using restic backup to backup some files to dropbox. Over the last few months, the backup commands would reach the end of the upload stage but hang and not fully complete. I tried this with a few other directories and it seemed to do this relatively consistently but didn’t have time to fully diagnose the issue. Recently, I’ve needed to restore from these backups but since they never completed the snapshots weren’t made. I never ran prune, so I tried to run restic recover, which found nothing. Running repair index was able to find a decent number of unindexed pack files, but didn’t change the result of restic recover. Is my data from those backups likely unrecoverable?
What does that mean exactly in term of messages printed by restic?
If running restic recover after a previous restic repair index run doesn’t create a new snapshot then you’re likely out of luck, sorry.
1 Like
Basically it’d get to the point where the backed up files and data matched the total files and data, but it’d just… stop? The timer would still go up so it wasn’t completely frozen or anything, it just wouldn’t move to the next step.
Ah k, it was worth a try.
1 Like
That usually means that some data is still waiting to be uploaded. Most likely the tree blobs that would have been required by recover.
A backup is only guaranteed to be restorable once backup prints that it has save the snapshot.