Posts by linesquarecube

Thanks a ton for the hint about sshfs – it works perfectly fine!

I've read a lot in different forums and other sources, but I never came across sshfs as a solution to this problem.

Just out of curiosity, I’ll also try to get the regular NFS mount working. I already tried again as you explained: first mounting the borg repo, restarting the NFS service in OMV, and also unmounting/remounting the share on the client. Unfortunately, I still run into permission issues. I can see the mounted folder, but it appears empty, whereas the same folder (borg_backup) mounted via sshfs works fine.

ls -l shows the following output:

drwxrwsr-x+ 2 root     users 4096  1. Sep 19:39 borg_backup
drwxrwsr-x+ 2 <myuser> users 4096 22. Aug 23:30 testfolder

It seems I don’t have permission to view the content on the client.

Quote

Guessing you are a windows user so I would try WinSCP

I'm on Linux, and similar to your suggestion of using WinSCP, I currently use scp or rsync over SSH for single files—depending on where I want to restore them.

Quote

Otherwise, you are mounting the archive on a shared folder. You could share that shared folder via nfs or samba. You might have permissions issues though.

I've already tried mounting the share via NFS, but encountered permission issues that I couldn't resolve. Since I read that Borg mounts are FUSE mounts accessible only on the host, I abandoned that idea. I also tried accessing the Borg repository with Pika Backup, but haven't had the time yet to fix some access issues. However, I suspect this solution might also be infeasible, as I haven't been able to access the OMV Borg repository from outside.

Do you know if it's possible to access mounted Borg repositories when using the File Browser plugin? I understand that File Browser is currently unmaintained, but since OMV runs locally, there shouldn't be any security concerns.

If none of these options work, I'll give command-line file managers a try

Hi everyone,

I’d like to hear your ideas or best practices on how you browse/access your BorgBackup archives when you’re looking for individual files.

Since the repositories are mounted via FUSE, sharing them to a client (e.g. a laptop) seems to cause access issues / empty folder views, at least as far as I understand.

At the moment, I usually mount the repo, navigate to the files on the OMV machine via the command line and copy them from there. Alternatively, I sometimes extract a specific archive and then browse it on my computer.

I’m wondering if there’s a more elegant way I might be missing. The command line works fine for finding/copying single files, but it would be nice to be able to browse archives with a regular file manager. I know there are CLI-based file managers, but I’d prefer something simple enough that I can show my relatives how to use it .

Thanks in advance!

great! thank you

I wanna send info like backup name, date/time of the backup, number of files, backup size, and success status over to Home Assistant to get a simple overview of my backups there.

If there’s no easy way to have these options, I’m thinking about creating a Python log parser to extract the info. JSON output would’ve been easier, but I’m fine with doing the extra work.

Hi,

I want to play around with some of the Borg options to get more value out of the log files. I've read that I have to add options like --json to each backup job, for example in the command borg create ... --json. Maybe a silly newbie question, but I’m not quite sure where exactly to put those Borg options in the plugin

Thanks for any help and advice!

Thanks for your instant reply!

Quote from ryecoaaron

Why do you only want to keep one backup? Since borg compresses and deduplicates, additional backups are unlikely to use much/any additional space.

Maybe it’s just old thinking from using rsync

Quote from ryecoaaron

Borg actually won't run hourly if hourly is set to zero. If you tell it to only keep one daily, then it will keep the one it just created.

Quote from ryecoaaron

The file time isn't important. Borg will run a backup for daily. It then runs the prune. If you have keep daily set to 1, it will keep the most recent archive which is the archive it just created.

These two things confuse me a bit... maybe I misunderstood something here.

Does this mean that if I set retain hourly to zero and retain daily to 7, Borg runs only once a day and keeps that backup (plus the next 6 backups) until the 8th backup is created and the oldest one is pruned — did I get that right?

But when exactly is the backup created if it’s not running hourly or at a specific time?

Thanks for all the explanations and for the time you invest in helping others learn!

Hi,

just a quick question to better understand how the Borg plugin works. I’m currently switching from basic rsync backups to Borg. Since the plugin is designed to run hourly, am I correct in assuming that only the last backup of the day at 11:00 pm is kept if I set the retention policy to keep one backup per day?

My use case is basically backing up pictures from my phone and documents from my laptop, which are synced throughout the day to an OMV share. Previously, I ran a basic rsync task at 3:00 am to ensure no data changes while backing up.

From what I understand, with the hourly backup strategy I achieve the same goal; the only difference is that files synced after midnight are included in the next day’s backup, as backups during the day will be pruned.

Thanks for your reply

Just to keep everyone updated who might stumble upon this thread: the issue for me was not directly related to OMV or Proxmox. The USB adapters I use for my drives do not work with UAS drivers. After reading this post in the Proxmox forum, I turned off UAS for the related drives, and everything is working fine now.

Thank you for that hint. As I've set up all my Rsyc tasks just yesterday and since this morning the OMV VM is not starting anymore, I also think about a Proxmox issue.

Do you know about any best practices which should be considered when setting up OMV in Proxmox?

Thanks for you answer in advance

Hi everyone,

I recently moved from a Raspberry Pi 4 with 4GB RAM to a machine running Proxmox, where I installed OMV in a VM. Everything seems to work as expected, except for my RSync tasks. Whenever there's a large file (e.g., greater than 2GB), the OMV VM crashes without any information written to the logs. I can only see the name of the last file that started to sync. I've already assigned 8GB of RAM to the VM, as I noticed that RAM usage increases significantly when RSync is running, but this didn't help at all. Has anyone experienced similar issues and can offer advice on how to solve this problem? On my Raspberry Pi setup, all my RSync tasks ran without any issues.

Happy for any advice