rogman

You're almost at the point the wine web GUI will be obsolete and everything can be done on the Web pages. I truly thought there was nothing else you could think of and every update it's fun to see what's changed. The push update comes in that an update was installed and it's like Christmas opening to see 🤣 Edit: reading your changes answered my question about the Z: mapping, thank you! I'm curious if others have had that issue of removing or changing mapped drives and they are removed from the container settings but the symlinks still exist in the app data folder, can that be fixed by running bb-doctor --fix and it safely remove those non used links?

@foz Got a question for you and a tip for others. I removed a drive map from my Docker template because I no longer needed that folder backed up. I ran bb-doctor, and it said I had an unmapped drive that showed as a warning. I couldn't see this drive because I removed it from the template. However, I looked into the AppData folder structure and found where drives are mapped and simply deleted that old one from the list, and the warning cleared. It was found here That's the tip for everyone. My question is: I never mapped the Z: drive, and I don't remember when I first noticed it. It is not a folder I'm backing up, but when you look in it, you see the container file structure. Is it safe to delete this folder from the \dosdevices\ folder, or is it supposed to be there? The folder shows root as owner

@DevanteWeary If you are synced and backing up, it should be safe to switch to beta. You can run bb-doctor from the Tools tab when you're up and see if any warnings/errors show up.

I was going to look into bbnotify.py, and when I pulled it up, it said just modified. Saw the Pushbullet info inside and ran to check for an update Great feature adding the manual entry field. At this point, it's not what this container does, but rather what it does not do?! I can't think of anything else. 10/10

@foz You are amazing, it's working now!

@foz What you've turned this container/project into is nothing short of amazing. I feel bad for the people who don't know about what you've created and how useful and polished it is! My backup finally finished fairly recently, and daily backups are now a breeze. I would still be uploading if not for your hard work and pure intellect that you have demonstrated, finding/fixing/improving the core upload speed issue, and now the plethora of nice features this project has with the API, web dashboard, diagnostics, etc. Thank you again for sharing your smarts with all of us users! I have been trying to get notifications to work via Pushbullet, which uses a bearer token and a JSON object, but I'm not getting the test to work. It looks like it should work with the settings you provided, but I can't get it to send. Here is what the dev console shows Pushbullet documentation provides an example template which reads as -- HTML POST /v2/pushes HTTP/1.1 Host: api.pushbullet.com Authorization: Bearer <your_access_token_here> Content-Type: application/json { "type": "note", "title": "App Alert", "body": "This is a notification from your custom application!" } -- Python import requests import json def send_push_notification(title, body): token = "YOUR_ACCESS_TOKEN" url = "https://api.pushbullet.com/v2/pushes" headers = { "Authorization": f"Bearer {token}", "Content-Type": "application/json" } payload = { "type": "note", "title": title, "body": body } response = requests.post(url, data=json.dumps(payload), headers=headers) if response.status_code == 200: print("Notification sent successfully!") else: print(f"Failed to send notification: {response.text}") # Usage send_push_notification("Server Alert", "CPU usage is above 90%!")

@foz I have a somewhat selfish request. Is it possible (with minimal work) to add a BB-Doctor tab on the Web GUI that can run the doctor and output results on the HTML page directly? If that was viewable from the Web it would make everything reachable all in one spot, like the skipped files is now (Thank you for this!!)

@foz The dashboard plugin with API Pause/Resume is fixed and working in current version

Backblaze does manage the memory but I don't think it spills over to the swap space until your ram is full or near full. I don't believe there is a way to force it to use it. Maybe if you limited your container to only use X GB RAM it could force it over to swap before your system runs out of memory. I know @foz has swap in use in some of his screenshots so he would be in the know on this issue.

I could be wrong, but I think as you get to larger and larger file sizes being backed up, your memory usage grows. That might be contributing to your issue and why you haven't ran into it before. It might be beneficial to setup and use swap space on an SSD or HDD to make up for the limited RAM availability. It also makes it worse when the scan is running that list of all your 2.3M files gets loaded into memory. If you are using encryption, that also increases memory usage. Lowering your threads would reduce some memory usage. Maybe try automatic, or set it to 8-10? The swap file would be what you have mapped for "Temporary Data Drive" on the settings tab in the GUI. You could map a folder on an SSD to your container as a new drive letter and try setting it to that. I might be way off on this, but it wouldn't hurt to try.

Yes try that first You'll get much much faster uploads too!

Did you set latest repo or the beta. ghcr.io/iamfoz/backblaze-personal-wine:beta

Did you try opening the web GUI and using the API tab from there? Not the terminal monitor. Whatever your web UI port is set to in docker template open in browser https://localhost(unraid-IP):5800(web port) eg https://192.168.1.5:5800 then click API tab. Select read and read:files permissions and Create key. Try that

I think the important thing is not to delete the .bzvol folders on your drives, as that will delete your backup. Once you map all the drives the same and inherit the backup, it should come up just like it was. If you're trying to use the dash plugin, note that it currently only works with the beta release of Backblaze64 (set the repo to ghcr.io/iamfoz/backblaze-personal-wine:beta in the docker template).

No you should probably use a new app data folder since they will be different files