I am closing this thread as solved, with this answer:
You can temporarily add it to the borg cron jobs in /var/lib/openmediavault/borgbackup but it will be overwritten by the plugin if you make in changes in the web interface.
Thanks for all.
I am closing this thread as solved, with this answer:
You can temporarily add it to the borg cron jobs in /var/lib/openmediavault/borgbackup but it will be overwritten by the plugin if you make in changes in the web interface.
Thanks for all.
ok, I am back now.
I would be curious if debug really tells you why. If something is failing, you shouldn't need debug to see that.
You're right, it didn't work for me.
I found out that the post script in the Borg plugin is executed before pruning the repository.
Is that a reasonable order?
My problem is that the post script should shut down the machine.
If I back up several repos one after the other, there may be a timing problem
and the remote backup server goes down while borg wants to backup the next repository.
I'll see if I can find a smart solution for this.
Any recommendation is welcome.
Thank you!
It would be helpful if the plugin offered an input for extra options.
Would be nice to find it in a future update, whenever.
BTW, why --debug?
I run backups on multiple repos every night, but it stops after the third one without an error message.
How do I add a logging level '--debug' in the borgbackup plugin?
There is a dead link in the menue: Services|BorgBackup|Repos|Docs|omv-extras wiki
Where did it move?
I am quite sure it was alive, few months ago
After updating to Version 6.8.0-1 (Shaitan) it works again
Check your system time and have a look into syslog to look out for errors from collectd.
You can usejournalctl -u collectd.service
I found this message:
Aug 08 00:00:43 serv1 collectd[2435813]: plugin_read_thread: read-function of the `df' plugin took 15.837 seconds, which is above its read interval (10.000 seconds). You might want to adjust the `Interval' or `ReadThreads' settings.
I have a remote backup server and use borg.
The backup server should only run when borg is active.
I start the backup server with WOL.
I would like to use autoshutdown to shut down the server after borg is finished.
How do I have to configure autoshutdown?
Use omv-firstaid and check if the RRD databases are invalid.
All RRD database files are valid.
You must enable monitoring in System | Monitoring -> Enabled
Monitoring was already enabled
Well, of course I have backed up my data.
But if the system drive or the backup drive crashes, the data is gone.
That's why I have RAID1, too.
Does that make sense?
Yes, it is to protect the operating system of my backup server.
I had a crash and it took a while to restore the system and get access to the backup data again.
I don't want to do this exercise again.
Here is the solution:
The non-booting was due to the BIOS settings.
I have an Asrock J3455-ITX motherboard and found some tips there: https://extreme.pcgameshardwar…m-laufen-bekommen.458941/
-> Disable TMP, disable CSM and set all settings to legacy mode, especially USB.
Now it boots.
Before I installed Debian 11.7 and set up this partition table:
finally used:
dpkg-reconfigure grub-pc
as mentioned here:
Does this help? https://wiki.debian.org/DebianInstaller/SoftwareRaidRoot
now, Debian is running in RAID1 mode.
Last, I installed OMV as shown here: https://docs.openmediavault.or…stallation/on_debian.html
Done!
Does this help? https://wiki.debian.org/DebianInstaller/SoftwareRaidRoot
Unfortunately not.
I followed the instructions without any errors.
Nevertheless, the PC does not boot.
I tried another set of instructions:
and
Debian Installation with LVM RAID 1 and Hot Spare – TuxFixer.com
both, the PC does not boot.
I have also considered this.
I haven't found anything helpful to install Debian in Raid1 with UEFI.
Any tip?
Hello!
I want to install OMV on a software RAID1.
I have found tons of descriptions but nothing works with UEFI.
Is there a tutorial or an explanation?