gabeduartem

it worked, thanks a lot! :)

Hey everyone! Yesterday my NAS started having random failures so I decided to give it a reboot, and now it doesn't boot anymore. I suspect there's something going on with the USB, because when I plug it on my computer, all the files are there, but its reeeeally slow and unresponsive. I ordered a new one which should arrive tomorrow, but I'm looking into how to smoothly move my installation to the new one, and I'm testing with some USBs I had laying around here. I downloaded a backup from Unraid's website and used the tool to flash it into the USB selecting the zip, but it seems like it just ignored all of my config, it got the default "Tower" name, and I couldn't access it using the IP that shows on the boot screen. I could ping it just fine, but doing a curl just gave me a connection refused error. I then checked the contents of the USB, and noticed that indeed most of the files on the config folder were not copied out into the new one, not sure why. I tried manually copying it onto the new USB and tested it out briefly and it seemed to get the configs, the arrays, and the tower is now named as it was before. I could access it using the IP, I just couldn't bring the array up again because of the license (I'll wait to do it on the proper drive to avoid blacklisting this one) So, the question is, can I safely copy the config folder from my old boot drive to the new one? Are there any other folders I should copy, like drivers, etc? I noticed some warnings about not finding the NVIDIA ones, etc, so I guess it wasn't just the config that wasn't copied. The driver I could probably just install again, I'm just concerned about potentially other missing stuff Thanks in advance!

I see... Thanks, I'll be keeping an eye on the issue!

Ahhh, bummer, I misinterpreted it then... It would be nice if it worked that way So, currently, it is not possible to programmatically decide if the backup should start or not?

Hey all! I have the plugin configured to run backups at a specific time, but I'd like to avoid backing up when I'm using a specific virtual machine inside unraid. I've created a script that exits with code 1 if that VM is running, and 0 if it is not, then I chmoded it, and added it as a custom pre-run script. When the plugin runs, it warns that the script exited with code 1 when the vm is running, but the backup does not stop. I assumed from the config that the backups would only continue if the scripts exit with code 0, since the header mentions something like this: "Custom scripts | Those must return exit code 0 for success detection". I also tested with pre-backup, but the same thing happens. Am I doing something wrong? Is it possible to achieve what I'm trying? Just for completion sake, here's the script ```sh #!/bin/bash VM_NAME="Windows 11" if virsh list --name --state-running | grep -q "^${VM_NAME}$"; then echo "VM '${VM_NAME}' is running. Backup aborted." exit 1 fi echo "VM '${VM_NAME}' is not running. Proceeding with backup." exit 0 ``` and here's the log from the pre-backup run with some things redacted: ``` 05.03.2025 08:38:03][ℹ️][Main] Executing script '/[...]/pre-backup.sh' 'pre-backup' '/[...]'... [05.03.2025 08:38:03][ℹ️][Main] Script executed! [05.03.2025 08:38:03][⚠️][Main] Script did not returned 0 (it returned 1)! [05.03.2025 08:38:03][ℹ️][Main] Method: Stop/Backup/Start [05.03.2025 08:38:03][ℹ️][...] Stopping [...]... done! (took 1 seconds) [...] ```

Ah, I see... Looking forward to when it gets implemented then, would be very useful for de-duplication purposes Also, I assume there's no way yet to do `post-backup` scripts per container? I'd love to tap into the plugin's workflow and while the containers are stopped also manually do DB backups. Without that, I'd have to again stop the containers (and manually handle that logic), causing more downtime...

Is it possible to avoid creating a tar archive and just create a folder instead? I can disable the compression, but it still creates the tar file... I have an external backup service that has file deduplication enabled, but it won't work with .tar files, but I think it would if it was just normal folders...