Migrating from resticprofile

[drguildo]

Hi. I'd like to migrate from resticprofile. If I use the same B2 repository URI, keys etc. as resticprofile, will I have to re-upload my data, or will backrest be able to re-use the existing data?

[mmuffins]

I'm trying a similar thing where I have an existing repository on Backblaze B2 that was set up and has snapshots that were managed by resticprofile. I'm trying to import that repository to backrest.
But I am having very little success. I set up all the necessary parameters, including the repository password and the AWS credentials. Backrest is able to connect to the repository. But for some reason, it tries to reinitialize the repository and fails because it tries to reinitialize the repository:

[unknown] failed to init repo: command "/nix/store/...-restic-0.18.1/bin/restic init --json -o sftp.args=-oBatc..." failed: exit status 1
Output:
{"message_type":"exit_error","code":1,"message":"Fatal: create key in repository at s3://<removed> failed: repository master key and config already initialized\n"}

I'm not sure if that is intended behavior and if backrest just tries to fully tries to manage every repository.. It might be related that the application key I gave backrest only have read permissions since I want to use backrest only to monitor backups, at least for the time being, but it seems weird that it is trying to initialize the repository again if it already exists regardless.

[mmuffins]

I was able to make some progress by directly editing the config backrest config file. I took an existing config and filled in the details for my B2/S3 bucket:

    {
      "id":  "backblaze-b2",
      "uri":  "s3://<endpoint>/<bucket>",
      "guid":  "<guid>",
      "password":  "<repository password>",
      "env":  [
        "AWS_SHARED_CREDENTIALS_FILE=<path-to-aws-credentials>"
      ],
      "prunePolicy":  {
        "schedule":  {
          "disabled":  true,
          "clock":  "CLOCK_LAST_RUN_TIME"
        },
        "maxUnusedPercent":  10
      },
      "checkPolicy":  {
        "schedule":  {
          "disabled":  true,
          "clock":  "CLOCK_LAST_RUN_TIME"
        }
      },
      "commandPrefix":  {
        "ioNice":  "IO_BEST_EFFORT_LOW",
        "cpuNice":  "CPU_LOW"
      }
    },

The guid can be found by running restic cat config for the existing repository. The credentials file looks like this:

[default]
aws_access_key_id=<appkey_id>
aws_secret_access_key=<appkey_secret>

With this the repository shows up fine in backrest and can be edited like normal. But it appears like backrest really wants have write permissions, even just to verify the repository connection. If I give it an appkey that only has read permissions on the bucket, the repo validation fails with

client.PutObject: not entitled
unable to create lock in backend: client.PutObject: not entitled