Skip to content

S3 Glacier #2817

@edpichler

Description

@edpichler

Guys, I really need to use Glacier to do backups.

I am doing it, but I get this message sometimes.

image

I would like restic has a feature that wherever this happens, he ask me if if I want to request the file to be restored from Glacier to S3 so I can try run again later.
Then in some hours I can try the backup again.
Restic don't need to wait the file to be restored. Once it's restored, it will follow the s3 lifecycle and stay available for some days.

This feature would make restic unbeatable. By far the cheapest way to do backup.

Something like restic backup --always-restore-from-glacier=yes

I don't know how to program in go. I if knew I could try to change the code.
Also, instead of listing just the prefix of the s3 file that is on glacier, he could list the entire file, so I can parse the errors and try to fix it if other script to try again restic later. I have many files...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions