26
Automating Restic backups (feldspaten.org)
submitted 1 year ago by to c/selfhosted@lemmy.world
13 comments fedilink hide all child comments
 

I'm having trouble automating the restic backup using systemd.

I followed the linked guide, which seems pretty straightforward. Backup works fine when I run it manually, but when I try to run systemctl status restic-backup.service I get the following error: Fatal: parsing repository location failed: s3: bucket name not found

I have triple-checked the file paths, and also added PassEnvironment=AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY RESTIC_REPOSITORY RESTIC_PASSWORD_FILE B2_ACCOUNT_ID B2_ACCOUNT_KEY to the restic-backup.service file, which I saw used elsewhere. This is my first time using systemd, so I'm not sure if I am overlooking an obvious step or what.

OS: Xubuntu

restic: installed locally following these steps

backup: Backblaze B2 bucket with s3

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 2 points 1 year ago

I was using s3, and I added the b2 variables in a "throw everything at the wall and see what sticks" process. not a good idea, but I do try to fix things on my own before posting things here. Occasionally I can figure it out lol. I've removed the b2 variables.

It occurs to me that I have restic set up as an app in backblaze according to this, so I'm not sure how it knows which bucket to use. appending the bucket name to the url does not change the outcome.

Now I am also getting: Fatal: unable to open config file: Stat: 401

  • permalink
  • fedilink
  • source
  • parent