Backblaze is not backing up the available data

[Rowdy]

I'm running this container on my Synology DS 1621+ with DSM 7.2. I've reinstalled my machine and decided also to start fresh with the backblaze backup. On my "old" setup before I've mapped every "shared folder" to an individual drive which worked just fine. Now I'd like to just use /volume1:/drive_d/ which should work also fine, right?!

I'm using the root user since my "normal" docker is not able to create files (at least the backblaze gui is prompting that).

root@home:~# id
uid=0(root) gid=0(root) groups=0(root)

docker-compose.yml

version: "3.2"
services:
  backblaze:
    image: tessypowder/backblaze-personal-wine:ubuntu18
    container_name: backblaze
    init: true
    volumes:
      - ./:/config/
      - /volume1:/drive_d/
    ports:
      - 5800:5800
    environment:
      - USER_ID=0
      - GROUP_ID=0
      - TZ=Europe/Berlin
    restart: always
    networks:
      - proxy

networks:
  proxy:
    external: true

Drive D is available and selected in the gui:

root@home:~# docker exec --user app backblaze ls -la /config/wine/dosdevices/
total 12
drwxr-xr-x 1 root root  12 Jun 15 19:42 .
drwxr-xr-x 1 root root 168 Jun 23 21:53 ..
lrwxrwxrwx 1 root root  10 Jun 15 19:39 c: -> ../drive_c
lrwxrwxrwx 1 root root   9 Jun 15 19:42 d: -> /drive_d/
lrwxrwxrwx 1 root root   1 Jun 15 19:39 z: -> /

I've no idea what the problem is.
If I select the drive D, the amount of files and data of "selected for backup" increased but just only to 7GB. There are 14TB waiting to be uploaded...

Any ideas? Help would be highly appreciated.
Thanks in advance.

[Rowdy]

I've just deleted the docker config folder and set it up completely new. Same result :-(

[jsdukeboy08]

I am having the same issue on a Synology 1221+ after updating to 7.2. The container has access and can see my folders/files but the backblaze client won't upload them.

UPDATE: I was able to get this to work on DSM 7.2 by having the config and drive_d folders on the same volume as my media. Previously it was installed on my NVMe volume with the rest of my docker containers but for some reason it does not work for me since 7.2 update when on a different volume.

[valan]

very similar issue here, files show up fine in wine explorer or a file picker in backblaze, but backblaze sees drive d, but no files get picked up. I'm also using uid 0 gid 0

[JonathanTreffler]

I cannot help with issues on Synology, as I do not have a machine to test it on, but good luck to everybody.

[valan]

I should add that I'm not using Synology, just a proxmox lxc running docker

[0xEmma]

Having same issue here, previously suggested solution didnt work.

[henryyeh]

I got to work with Synology by execuing into the container and chowning the symlink for drive_d to app instead of root. Also, I used the ubuntu18 image instead of latest. DS1621+

[0xEmma]

I got to work with Synology by execuing into the container and chowning the symlink for drive_d to app instead of root. Also, I used the ubuntu18 image instead of latest. DS1621+

Which file? /drive_d, /config/wine/dosdevices/d: ? tried both but both are still owned by root:root. Im using user_ID and group_Id of 0 else it wont start.

docker run     -p 8080:5800     --init     --name backblaze_personal_backup     -v "/volume1/:/drive_d/"  -e USER_ID=0 -e GROUP_ID=0   -v "/volume1/SynInternal/backblaze/:/config/"     tessypowder/backblaze-personal-wine:ubuntu18

all files show in the "exclusions" file selector, and are accessible by the "app" user

[henryyeh]

First of all, make sure you're running the tessypowder-backblaze-personal-wine:ubuntu18 image

I see that you have 777 on /config/wine/dosdevices/d: but like I said in my previous post, I had to chown it so it was owned by app for it to work:

My /drive_d is also owned by app:app 755

[0xEmma]

First of all, make sure you're running the tessypowder-backblaze-personal-wine:ubuntu18 image

I see that you have 777 on /config/wine/dosdevices/d: but like I said in my previous post, I had to chown it so it was owned by app for it to work:

My /drive_d is also owned by app:app 755

I wonder if the difference is I'm mounting /volume1 rather then a specific folder. I shared my docker run in my post above

[henryyeh]

I wonder if the difference is I'm mounting /volume1 rather then a specific folder. I shared my docker run in my post above

That might be it, I believe you have to mount a Synology shared folder. Also, go exec into your container and do a chown app:app /drive_d and the same for the symlink in the config directory.

[0xEmma]

I wonder if the difference is I'm mounting /volume1 rather then a specific folder. I shared my docker run in my post above

That might be it, I believe you have to mount a Synology shared folder. Also, go exec into your container and do a chown app:app /drive_d and the same for the symlink in the config directory.

Makes no difference sadly, also tried changing the APP_USER to root with no luck.
Also tried mounting via NFS to another system, and running it on there - same issue