3 ms·
Did you test the backups with Restic's built in test command, or by restoring?
by StavrosK 6y ago
Did you test the backups with Restic's built in test command, or by restoring?
- chenxiaolong 6y agoI tested by attempting to do a full restore to a temp directory.
- StavrosK 6y agoDo you remember if `restic check` said that everything was fine?
- chenxiaolong 6y agoUnfortunately I don't remember. From the (little) notes I kept, the corruption occurred with restic version 0.9.3. I had also tried restoring with the latest code from git master, but I didn't make a note of the exact commit (it didn't make a difference anyway). The commands that triggered the corruption were the following. I tested the restore around the 10th run of this. repo=sftp:chenxiaolong@<ip address>:/home/restic restic -r "${repo}" backup -x /home restic -r "${repo}" backup -x --exclude /stuff/Android/AOSP /stuff restic -r "${repo}" forget --keep-last 3 --prune