Open ossie-git opened 2 months ago
Restic appears to be able to run snapshots
on the repository:
$ restic -r /mnt/hard/O/Backups/Rustic/AWS/ snapshots
enter password for repository:
repository 9fd2c6f9 opened (version 2, compression level auto)
created new cache in /home/o/.cache/restic
Ignoring "7f008c6609065eb9a03134440168bebe280b4b0b6f56c6f6b0c6876f2e175915": failed to load snapshot 7f008c66: invalid data returned
ID Time Host Tags Paths
----------------------------------------------------------------------------
5f7097a5 2024-05-14 16:20:59 dell /home/o/Downloads/AWS
c6fa2e44 2024-05-14 16:21:03 dell /home/o/Downloads/AWS
fbf9571d 2024-05-14 17:40:01 dell /home/o/Downloads/AWS
...
Seems like the snapshot file 7f008c6609065eb9a03134440168bebe280b4b0b6f56c6f6b0c6876f2e175915 is defect.
So yes, the error message should be improved such that you can see where data decryption failed. Also we could ignore defect snapshot files like restic does. These are IMO good UX improvements.
@ossie-git Can you please post the output of rustic check
? There at least some useful information should be given, it not this is a UX bug, IMO.
$ rustic -P aws check
[INFO] using config /home/o/.config/rustic/aws.toml
[INFO] repository local:/mnt/hard/O/Backups/Rustic/AWS: password is correct.
[INFO] using no cache
[00:00:00] reading index... ████████████████████████████████████████ 24/24 [00:00:00] listing packs... ⠁
[00:00:00] listing packs...
error: data decryption failed
@ossie-git Thanks. This is not how it should be :wink:
Do you have any idea why the backup might have become corrupted. I'm just guessing but it might have been right as I was suspending my PC
Hi,
I have a repository that suddenly won't allow me to list snapshots. It was working fine before today. This is what I see when I run a
snapshots
command:Other commands such as
find
also don't work (I'm using the nightly builds):At the same time, some commands such as
backup
do work:and:
I'm currently using the following (as I want the
find
command):I also downloaded and tried it on the stable version and have the same problem:
My configuration is very simple (I have another repo with the exact same configuration options which is still working fine):
Any ideas? Thanks