PanicMechanic007

Thanks so much for the suggestions and kind words mate. I’ve tossed all your ideas straight into GitHub issues so they don't get lost in the forum void. Honestly, having to juggle different backup apps, custom user scripts, and an rsync prayer just to back up appdata, VMs, and shares was driving me nuts. That exact "why is this such a massive pain in the ass?" moment is literally the whole reason Vault was born. I just wanted one tool so I didn't have to play air traffic controller every time I wanted a backup. Really appreciate the support and feedback while I keep chipping away at it! Cheers!

Thanks for the detailed feedback and kind words - I really appreciate the support for the plugin! Here is a quick breakdown on the points you raised: "Largest Backups" Widget: Thanks for pointing that out. I'll review how backup sizes are queried for the widget so that incremental runs don't overwrite the reported total size with just the latest delta. Scope & Troubleshooting: Just to set realistic expectations - Vault is a passion project built and maintained specifically for my own modest Unraid setup (a few basic containers). Because my home setup is pretty minimal, I don't have the infrastructure, synthetic test data, or remote storage destinations (like Koofr or Backblaze) required to reproduce or debug 250GB+ transfer stalls. While I'll keep general stability and resilience in mind for future updates, I unfortunately can't offer hands-on troubleshooting for individual environment or network bottlenecks. That said, the code is open source - so hopefully someone in the community experiencing similar upload bottlenecks can dig into the code, spot the bug, and submit a fix! Resource Controls & Robustness: Adding settings to cap/control resource allocation (CPU/RAM) and implementing better timeout or auto-recovery handling when a transfer stalls are great suggestions. Making the plugin more resilient against unexpected network/storage anomalies is on the priority list. Browser Note: I personally stick to Chrome and Safari so I haven't run into the Brave issue myself, but thanks for sharing that site-data workaround for any other Brave users who might hit it. Thanks again for taking the time to share your logs and feedback. Cheers!

Thanks for the feedback. 👍🏻

Thank you. Good to know the browser fix is working. 👍🏻

Thank you. I will check the logs and make some adjustments to the code.

Hello, thanks for sharing the issue. I'll have a look at the logs and see what's causing the issue.

Hello, under settings you can download a diagnostic log. That will help to troubleshoot the issue.

Thanks for the feedback. Much appreciated. I will make improvements.

What’s the errors? Please share

Hello, I'm making improvements to the DR process. Next version will allow you to go through the Recovery tab to recover your backup storage and restores your settings step by step.

Thanks for letting me know. I'll install the recycle bin plugin and implement improvements.

@Stan464 Should be fixed now in latest version. I have tested on 2 vms and working fine. Just make sure you convert raw disks to qcow2 format.

Hello @Stan464 Are these Windows or Linux VM's?, how many disks attached to the vms?, How many Nics?, Are they big or small vms? Are the disks raw or qcow format? Do you have the VM Guest agent running on them?

Great question - and you're not being stupid at all, the wording is a bit ambiguous! The tickbox means "back this up", not "exclude this". So: - Ticked = that path/data is included in the backup - Unticked = that path is left out - Greyed-out + "Auto-excluded" = Vault skips it automatically (media shares, remote shares, etc.) because those are usually huge shared data you don't want in an appdata backup, so I lock them off. For your example - to keep Config and drop UNR1/2/3 - UNR2 and UNR3 are already auto-excluded (they're /mnt/remotes shares), and you'd just untick UNR1. One thing I've spotted from your screenshot: your Jellyfin /config lives on an Unassigned Devices disk (/mnt/disks/...). Vault is currently auto-excluding the whole /mnt/disks/ family as "direct disk", which is wrong - appdata on an Unassigned Devices SSD should absolutely be backable. That's a bug on my side, not you. I'll get it fixed so that box is tickable. In the meantime, you can still protect that config by adding /mnt/disks/CTU-INTG-240GB-1/appdata/Jellyfin as a Folder backup - that path isn't auto-restricted, so it'll back up fine. Thanks a lot for the kind words and for flagging this!

Hello, I had a few issues with the notifications system but should be sorted out now in the latest version. BTW: If you use home assistant you can also use the vault integration to notify you of backup failures and do other automations. https://github.com/ruaan-deysel/ha-vault. Before using the HA Vault integration just make sure you set the plugin's bind address to your unraid servers IP address from drop-down list and get the API key from Vault --> Settings --> Security --> API Access. You will need that to setup the integration.