Hello, your error messages look very similar to OpenStack backend error: `conn.ObjectOpen: Object Not Found` . From what I can tell, OpenStack Swift seems to be unable to return the content of these two snapshots. You could try to access the file using the swift command line client, to make sure that these files are indeed inaccessible. If that is the case, the simplest way forward would be to delete the two damaged snapshots, this will just remove the corresponding snapshots but leaves everything else in place. In case the swift backend has a backup copy of the snapshots somewhere, you could also remove and then restore the snapshots.
Once these inaccessible files no longer show up in the snapshots ‘folder’, restic should be able to continue the backups. Please run a full restic check --read-data run to make sure that the remainder of the backup is intact (it’s probably ok as rebuild-index did work, but better be safe). That will also validate the full content of each pack file in addition to just checking the backup metadata.
You could also try the recover command which will search your backup for all existing directory trees in case you need some files included in the damaged snapshots.
You (or the backend provider) will definitely need to investigate why these snapshots can no longer be retrieved. It is a serious problem if the storage backend looses data; restic might become unable to restore some files or even whole directories if files in the data directory were to disappear.
P.S.: The anonymized paths/hostnames are fine.