Hey guys, I think most of the issues here is related to how you set up your plan.

See:

from https://garethgeorge.github.io/backrest/introduction/getting-started/

For example for my own plan the only difference here is that my path is /backup/some-cool-unraid-folder. The only mapping i have is /mnt/user/backup => /backup.

@matt020191 you may want to map /tmp to /tmp or /dev/shm to /tmp if it is filling up the container for some reason. It shouldnt be an issue in most cases unless you are backing up 10+TB in which case the cache/tmp may reach 100s of gigs. Using Docker directory instead of image would also fix this.

@xman111 this covers it: https://garethgeorge.github.io/backrest/cookbooks/ssh-remote

I'm not able to get Backrest working properly. I want to create a repo at the location /mnt/user/resticbackup and I want to backup shares in the /mnt/user folder, like for example /mnt/user/apps.

When I create the repo in Backrest I enter the path /mnt/user/resticbackup. When I click on Test Configuration it says "Connected successfully to /mnt/user/resticbackup and found an existing repo." However, there is nothing there yet. No repo is created when I click submit, and when I run a check on the repo it fails because the repo does not exist. Why is this happening?

Also, I'm not sure how to get the other shares to show when I create a plan. For some reason the "path" field does not autofill any further than "/mnt", which suggests it can't find anything beyond this.

Config attached. What am I doing wrong?

Backrest seems to be working great for me (this app template works well too). I only ran into one issue. /backup is mounted as read only, which at first makes sense as it normally wouldn't need write access just to backup. However, in testing to restore files I couldn't restore as again it's read only. Backrest wants to restore to the /backup directory by default. Because of this I would argue that /backup (Path to backup) be set at read/write by default so the app works as expected. Unless I'm missing something?

2 hours ago, zer0ed said:

Backrest seems to be working great for me (this app template works well too). I only ran into one issue. /backup is mounted as read only, which at first makes sense as it normally wouldn't need write access just to backup. However, in testing to restore files I couldn't restore as again it's read only. Backrest wants to restore to the /backup directory by default. Because of this I would argue that /backup (Path to backup) be set at read/write by default so the app works as expected. Unless I'm missing something?

Hey zer0ed, good catch. I've updated the template to make that RW by default. Also added a default /mnt/user/appdata/backrest/tmp:/tmp mount to the template which should solve issues with running out of space in docker.img. Existing users with the template shouldn't need to add it unless they are experiencing excess docker disk size from large chunks during restore/backup, or if they are running out of RAM.

@lococola , sorry - didn't see this, the issue is that inside of backrest you want to use the container mounted paths so /backup, /repos, etc. If you want you can just mount /mnt/user/resticbackup:/mnt/user/resticbackup then use the same path inside of backrest.