No Versioning, no backup.
You can use rsnapshot without the Plugin.
Use Something tested...
To keep more days/weeks/years of Backup with little extra space usage, use rsnapshot
Did I miss anything big, or are those the issues you were speaking to?
Nothing Special about OMV. It is an General advice. I would avoid the complexity.
BTRFS Supports RAID. So you do Not News the added complexity of mdadm.
Having said that, there are scenarios, in which a RAID5 in btrfs can be unstable (unclean shutdown PLUS a failed Drive)
Your Post ist very hard to read.
And: Don't Tell us all the Details, but only what could bei relevant.
Do Not Mix mdadm RAID with btrfs
Use the btrfs RAID Levels instead.
Inform yourself about the latest Status of btrfs and RAID 5 though.
With my RAID50 setup, I have 3x RAID5 arrays striped, so I can lose 3 disks at a time, permitting 1 disk per RAID5
And once you lose two in one Raid5 all Data ist lost.
Why ist this better than raid6?
Does it really make Sense to continue this mega Thread?
Solutions get lost in it.
If everyone opens one Thread per topic with a good descriptive Titel, it May lead to questions being answered only once rather than multiple Times.
So, why Not Close this one?
Macom ist right.
RAID is No Backup.
An accidentally deleted File is gone on both Drives.
Just to avoid Others to follows this advice:
Most likely the Kernel was not the fix.
Maybe the reboot or something Else was.
The advice to Upgrade the Kernel was most likely nonsense
Too little information.
Did you try Google?
I upgraded to 5.0 recently.
After the upgrade everything works fine, but I was missing the Unionfs page.
Now, in omv-extras, I find two plugins:
Unfortunately, I am not sure, which one I used before - I think it was unionfilesystems.
After installing both (expecting to find in one of the two to find my drives), I getCodeOMV\AssertException: The property 'self-mntentref' does not exist in the model 'conf.service.unionfilesystems.filesystem'. in /usr/share/php/openmediavault/config/configobject.inc:71#0 /usr/share/php/openmediavault/config/configobject.inc(186): OMV\Config\ConfigObject->assertExists('self-mntentref')#1 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('self-mntentref', '292655f9-8de7-4...', false)#2 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, false, false)#3 /usr/share/php/openmediavault/config/database.inc(85): OMV\Config\ConfigObject->setAssoc(Array, false)#4 /usr/share/openmediavault/engined/rpc/unionfilesystems.inc(142): OMV\Config\Database->get('conf.service.un...')#7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getList', Array, Array)
At each logon.
I found this thread, but it is similar only...
There, the suggestion is to remove the <mlimit>..
But I do not think that this makes sense here, as I think that the self-mntentref is needed.Code
I still get the same error.
Which of the two plugins should I use, and how can I fix this issue?
Zeig doch Mal dein Log nach dem awk kommando
I understand. Thank you.
I recommend running
This will return a list of backups
If a passphrase is needed, it will ask:
And then answerCode
If you add --json to the command, you will get a more suitable output.
I can only tell you the obvious and you should consider that the obvious is the answer.
And as you do not say why my answer is wrong/not applicable in your view, I cannot help further.
don't know how to get borg to use an existing folder when trying to make a new repo
And this is the problem: you should not create a new repo. You should just skip the step of creating a new one in case the user already has a repo. In that case, Borg will just use that.
I could easily add what I think is right
You could state that and then you would get feedback.
But you just ask not to state the obvious. How shall we do that, if we don't know what you deem obvious and also not, what you think is wrong with the obvious.