Discussion: How to support cold storages?
This issue is meant to discuss which is the best way to implement the support of cold storages in restic. The need to use restic with cold storages has been addressed in several places, see #1903, #2504, #2611, #2796, #2817 and several discussions in the forum. There are also some experimental PRs which kind of allow users to use cold storages, see #2516, #2881, #3196 and the already merged prune improvements (#2718 and following PRs) are already made to support cold storages in future. What should restic do differently? Which functionality do you think we should add? ---------------------------------------------------------------------------------- Allow users to use repository on some "cold storages". These are usually cheap (cloud) storages where writing is fast and cheap, storing data is extremely cheap, but accessing the data is usually extremely slow (or may even need some extra "warming up" before being able to access it) and/or expensive. Some cold storages also require minimum file sizes or are expensive for small files, but this is not specific to cold storages, so I would like to skip this in the discussion here. Examples of cold storages are: - AWS S3 Glacier and Glacier Deep Archive - Google Cloud Platform Coldline Storage and Archive Storage - Azure Blob Storage Cold and Archive - OVH Cloud Archive - Maybe self-programmed backends which write to a tape What are you trying to do? What problem would this solve? ---------------------------------------------
Posted by aawsome on Dec 30, 2020, 12:15 PM
Tags
Related issues
- Everything is too expensive for European bureaucrats.
- Yeah, the plan is far too expensive for what it provides.
- Crashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
- /dev/random is much too expensive for this.
- Yeah, this always bugged me.
- A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
pricing (Other)
Everything is too expensive for European bureaucrats.
NewYeah, the plan is far too expensive for what it provides.
NewCrashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
New/dev/random is much too expensive for this.
Yeah, this always bugged me.
A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
There's a talk from Travis Kalanick recently on a podcast about this.
Discussion: How to support cold storages?
This issue is meant to discuss which is the best way to implement the support of cold storages in restic. The need to use restic with cold storages has been addressed in several places, see #1903, #2504, #2611, #2796, #2817 and several discussions in the forum. There are also some experimental PRs which kind of allow users to use cold storages, see #2516, #2881, #3196 and the already merged prune improvements (#2718 and following PRs) are already made to support cold storages in future. What should restic do differently? Which functionality do you think we should add? ---------------------------------------------------------------------------------- Allow users to use repository on some "cold storages". These are usually cheap (cloud) storages where writing is fast and cheap, storing data is extremely cheap, but accessing the data is usually extremely slow (or may even need some extra "warming up" before being able to access it) and/or expensive. Some cold storages also require minimum file sizes or are expensive for small files, but this is not specific to cold storages, so I would like to skip this in the discussion here. Examples of cold storages are: - AWS S3 Glacier and Glacier Deep Archive - Google Cloud Platform Coldline Storage and Archive Storage - Azure Blob Storage Cold and Archive - OVH Cloud Archive - Maybe self-programmed backends which write to a tape What are you trying to do? What problem would this solve? ---------------------------------------------
Comments (0)
No comments yet. Start the discussion.