Upgraded from 1.2.1 to 1.5.0 and nothing is working?

[avpengage]

Discussed in https://github.com/garethgeorge/backrest/discussions/487

^{Originally posted by **avpengage** September 21, 2024} I upgraded 2 different docker instances from 1.2.1 to 1.5.0, now neither instance will backup or do anything really. Both instances use Backblaze as an S3 backend. On the repo, Unlock appears to work (doesn't give an error, pbut likely doesn't actually work?), but check returns: `Failed to check: : [unknown] check: check repo mbm2024: command "/bin/restic-0.17.0 check -o sftp.args=-oBatchMode=yes" failed: exit status 10` index returns: ``` unknown] get snapshots for repo "mbm2024": get snapshots for repo mbm2024: command "/bin/restic-0.17.0 snapshots --json -o sftp.args=-oBatchMode=yes" failed: exit status 10 Output: Fatal: repository does not exist: unable to open config file: stat s3.us-west-002.backblazeb2.com/config: no such file or directory Is there a repository at the following location? s3.us-west-002.backblazeb2.com ``` There is def a repository at that location, and it was backing up to it happily for 2+ months, until i just upgraded backrest... Basically nothing is working - is there some simple fix I'm missing? Any help or trouble shooting tips would be greatly appreciated. Thanks!

[garethgeorge]

Hey, sorry you're running into trouble here.

Backrest added some extra checks that it isn't implicitly creating repositories when trying to open them (e.g. to prevent a scenario where a user accidentally edits their URI and is then backing up to a location they're not aware of...) -- it's odd that you'd run into a problem here though if you've been successfully backing up for a while.

One thing that stands out to me is that the path s3.us-west-002.backblazeb2.com/config doesn't quite look expected. I'd think there should be a bucket name there somewhere -- did you edit your settings recently? Does your URI look correct?

[avpengage]

thanks for the quick response. Everything had been running nicely, then last night I figured I'd upgrade to the latest version, and nothing but trouble since :-(

In the container, in the config folder, there are a lot of old revisions of the config, all of them just have that s3 bucket. Here's the repo from the config:

{ "id": "backblaze", "uri": "s3.us-west-002.backblazeb2.com", "password": "xxxxxxxxx", "env": [ "AWS_ACCESS_KEY_ID=0021cb7c...", "AWS_SECRET_ACCESS_KEY=K002..." ], "prunePolicy": { "schedule": { "maxFrequencyDays": 1, "clock": "CLOCK_LAST_RUN_TIME" }, "maxUnusedPercent": 25 }, "checkPolicy": { "readDataSubsetPercent": 0 }, "commandPrefix": {} }

So I don't believe the config changed... I did try prefixing the uri with s3:// and s3: - neither made any difference...

I guess I was using restic 0.16 prior to this, now using 0.17 - nothing required on my part for that version change?

Any other ideas?

Update:

I just logged into backblaze and the bucket is now 0 bytes? This had to have had data in it, because I actually restored files from it about a month ago... It is possible I somehow deleted the contents by upgrading? Something to do with me not having something after the s3 address?

The other site I upgraded - its s3 bucket is also 0 bytes now? Also, all config files have nothing after the s3 address...

Thanks