azure: add support for access tiers hot, cool and cold#5046
Conversation
97669f6 to
4869b4a
Compare
|
Are we sure that allowing the archive tier is a good idea? It's latency can be on the order of hours, say the MS docs, so this seems to introduce a cold storage option without special support for getting the data back out. I mean, maybe you can set timeouts to multiple hours, but does that not cause other trouble? |
MichaelEischer
left a comment
There was a problem hiding this comment.
Are we sure that allowing the archive tier is a good idea? It's latency can be on the order of hours, say the MS docs, so this seems to introduce a cold storage option without special support for getting the data back out.
The archive tier definitely shouldn't be officially documented as supported. Right now, the S3 backend also allows setting arbitrary storage classes (including glacier / deep archive) but those are never explicitly mentioned in the documentation. Instead the changelog entry from https://github.com/restic/restic/pull/4584/files makes is clear that cold storage is not officially supported and may require manually warming up everything.
b16f0b6 to
bff3341
Compare
What does this PR change? What problem does it solve?
This commit adds functionality to control the access tier for Azure blob storage backend. This should support Online Access Tiers including Hot, Cool and Cold.
Only Data Pack files which are infrequently accessed will be stored in the selected access tier.
Was the change previously discussed in an issue or on the forum?
Closes #4521
Checklist
changelog/unreleased/that describes the changes for our users (see template).gofmton the code in all commits.