Skip to content

OVH Cold Storage #1744

@anayrat

Description

@anayrat

Hello,
It is not an issue, I just wanted to share my experience with OVH Cold Archive (different from Cloud Archive).

I created two buckets, on hot (metadata) and another cold (data):

Here is my ovh-cold.toml configuration:

[global]
#log-level = "debug"

[repository]
repository = "opendal:s3"
repo-hot = "opendal:s3"
password = "xxxxxx"
warm-up-command  = "s3cmd restore --restore-days=3 -dv s3://nas-cold/nas-cold/%path"

[repository.options]
endpoint = "https://s3.eu-west-par.io.cloud.ovh.net"
region = "eu-west-par"
access_key_id = "xxxxx"
secret_access_key = "xxxx"

# options only for hot part
[repository.options-hot]
bucket = "nas-hot"
root = "/nas-hot"

# options only cold part
[repository.options-cold]
bucket = "nas-cold"
root = "/nas-cold"
default_storage_class = "DEEP_ARCHIVE"

Notice the warm-up-command, I had to create an s3cmd config for my ovh bucket.

Here is the command I use to backup:

rustic  backup   -P ovh-cold --set-compression 12  /folder

If I want to restore:

rustic  restore   -P ovh-cold latest:"myfile"  /destination/

rustic will send warm up command for each chunk. I did not investigate how to send batch command.

Due to cold archive limitation, warmup take more than 48 hours. The first restore will fail and after 48H, you will be able to restore file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    S-triageStatus: Waiting for a maintainer to triage this issue/PR

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions