Backblaze Personal Backup Container: How to move .bzvol folder to cache to allow disk spin down

[nivrix]

Hi everyone,

 

I’m currently running a Backblaze Personal Backup container. In this setup, my entire user directory (/mnt/user/) is exposed and passed as a virtual drive to the Backblaze Personal Backup software through a Wine environment. Everything works fine so far.

 

However, there’s one thing I would like to change: I want my disks to spin down again. Currently, that’s not happening because the Backblaze container creates a .bzvol folder in the root directory of its virtual drive (/mnt/user/.bzvol). When I create a hidden folder in the Unraid user directory, it automatically gets placed on the first disk. This hidden folder is actively used during uploads, meaning that Disk 1 remains active constantly, even if the data is only being uploaded from the cache.

 

I’ve already tried deleting the .bzvol folder and recreating it directly in the cache array. The issue is that when I expose the user directory and mount it as a virtual drive in Backblaze Personal Backup, any write operations in this .bzvol folder are automatically directed to Disk 1, even though the folder was initially created in the cache. Creating a "hidden" share with primary storage to cache also does not work, because you cant start the share name with a dot.

 

I also tried working with symlinks. First, I created symlinks using the Unraid terminal, outside the container but they pointed to incorrect directory paths inside the container. Then, I tried creating symlinks directly within the Backblaze Personal Backup Docker container, but that didn’t lead to success either. To be more specific, I created a share called bzvol (/mnt/user/bzvol) and set its primary storage to cache. I then created the .bzvol folder here (/mnt/user/bzvol/.bzvol) and created a symlink from this .bzvol folder to the root directory of the virtual disk in my case the user directory (/mnt/user/.bzvol). Unfortunately, this didn’t work as intended either.

The only solution I can think of is to pass each individual share as its own virtual drive to the container. However, I would prefer a solution that includes the entire user directory so that new shares are automatically included without further adjustments.

Maybe someone has a creative solution for how to implement this. Any help would be greatly appreciated! Thanks in advance!

 

Link to project (Available in Unraid Community Applications): https://github.com/JonathanTreffler/backblaze-personal-wine-container

Edited October 2 by nivrix