Minio as cold storage provider - InvalidStorageClass

[benjaminpreiss]

Hey there!

I am trying to test a cold storage setup locally with minio, with the following rustic.toml config:

[repository]
repository = "opendal:s3"
repo-hot = "/persisted/rustic/repo_hot"
password = "your_encryption_password_here"
cache-dir = "/persisted/rustic/cache"

# options only for hot part
[repository.options-hot]

# options only cold part
[repository.options-cold]
bucket = "test-2"
root = "/backups"
# currently only default_storage_class = "STANDARD" works
default_storage_class = "DEEP_ARCHIVE"
endpoint = "http://minio:9000"
access_key_id = "rustic-user"
secret_access_key = "rustic-password"
region = "us-east-1"

This is quite obvious, as minio is not a cold storage provider.
So I wonder if I can run a rustic "cold storage" repo with storage class "STANDARD" and what the implications of that are for restores? Will rustic still run "restore" operations for files, or will it just access them?

Would be very grateful for insights on the topic, as I have a storage provider that provides me cold storage on top of minio. I reckon they provide the minio restore operation (https://min.io/docs/minio/linux/reference/minio-mc/mc-ilm-restore.html) to transition objects into a retrievable state.

[aawsome]

In the case of a cold repo, rustic will not read the data from the cold repository for most operations (like backup, forget, snapshots, ls) - but will create or delete new objects. Only for operations like restore, dump it will try to warm-up the needed files (e.g. using warm-up-command) after which it normally reads them.

So, yes, in your case using standard storage class and configure ILM to automatically "freeze" everything and configuring a warm-up-command which calls ilm restore could be the way to go!

[benjaminpreiss]

I am just wondering - what is the default warm-up command when using storage class STANDARD?
If I use ilm restore, do I need to install minio mc client?
Or is ilm restore part of the default s3 command set and therefore included in rustic?

[aawsome]

Hi @benjaminpreiss, thanks for the question!

In fact rustic does not have any default warm-up command. It just supports 2 ways of possible warm-ups. The first is to just try to access the file (ignoring potential errors) and the second is to use an external command, the warm-up-command. So, if your storage backend needs to change the storage class and doesn't do so by the simple attempt to access and object, you need to specify the warmup as external command - and of course you have to install everything what is needed to run this command on your system!