Posts by an0o0nym

    Right, sorry. I thought I made it too confusing.

    What if I take a simpler approach: stop all docker containers, back up the data volumes and then start all the containers again afterward? Would that be a more practical solution?


    If not what would you say is the best approach for my use case? I'm particularly interested in the best strategy for using the compose backup plugin when dealing with large external data volumes.

    To provide a bit more context, I am running my setup on an old PC with 2 HDD drives. One HDD (lets call it HDD1) is LUKS encrypted and used for data storage (all compose data volumes are mounted here) and the other (lets call it HDD2) is an unencrypted drive where I store borg-encrypted backups. I run OMV on a stick and I use an nvme ssd (120GB) for system data storage (including docker system/config files) - this is also where docker compose backup directory is setup.

    Currently I use the compose backup to handle docker directories backup only (excluding data volumes), which I plan to back up using the borgbackup plugin as you suggested.


    However I've excluded the data volumes on purpose (the largest being a few TBs) from the compose backup plugin because, if I understand correctly, it would replicate all data directories from my HDD1 to SSD, effectively using double the storage space and running out of space on SSD.



    Ideally, I'd prefer to stop the containers temporarily and perform a Borg encrypted backup of the Docker data volumes from HDD1 directly to my HDD2 and possibly to the cloud.


    I hope this clarifies what my goal is.

    Does it make sense at all, or did I just over complicate things?

    Hi,

    I'm currently using openmediavault-compose and I'd like to integrate openmediavault-borgbackup to back up my data from Docker volumes.


    Could you guide me on how to replicate the functionality of the built-in backup feature of openmediavault-compose? Specifically, I need to know how to stop services for specific compose services before initiating a backup and then how to restart them once the backup is complete. I would love to achieve this functionality to integrate with openmediavault-borgbackup.

    Quote

    Now syslog shows:

    Code

    Code
    Dec 15 17:39:03 omv-server monit[996]: Filesystem '/srv/dev-disk-by-label-data1' not mounted
    
    Dec 15 17:39:03 omv-server monit[996]: 'filesystem_srv_dev-disk-by-label-data1' unable to read filesystem '/srv/dev-disk-by-label-data1' state
    
    Dec 15 17:39:03 omv-server monit[996]: 'filesystem_srv_dev-disk-by-label-data1' trying to restart
    
    Dec 15 17:39:03 omv-server monit[996]: 'mountpoint_srv_dev-disk-by-label-data1' status failed (1) -- /srv/dev-disk-by-label-data1 is not a mountpoint

    I am getting the exact same logs in OMV. I just installed a fresh instance of OMV on my Raspi 4. Everything worked fine. I installed Encryption plugin and followed instructions provided in this post on the very first page. No problems at all - until I restarted the raspi.


    Now file system for that disk is marked as 'missing' and I get the logs as mentioned by KemikalElite . Can someone help to debug this problem and eventually find a solution?

    I have the exact same problem. Everything was working fine untill I restarted the machine. Now the disks doesnot show up in encryption plugin. The disk is seen in 'disks' section. However status in the file systems for that disk is 'missing'.

    EDIT:
    I am using OMV 5.x though.

    Quote

    You are using a Raspberry Pi and the pdf clearly states on page 39 that it does not apply to SBC's or i386 users.

    The Raspberry Pi is an SBC!



    I missed that note - my bad. Thanks for the help.




    I am enabling the extras repo because this one of the steps (optional but recommended) in the guide here https://github.com/OpenMediaVa…/Getting_Started-OMV5.pdf (page 41).


    I am not quite sure what it does though. I would expect it to work as source list on Linux?

    After uninstall OMV-Extras I downlaoded the .deb package for OMV-extra and installed it using GUI. The error is back again during the installation of OMV-extras:

    Hello there,

    I just installed my first instance of OMV today on my Raspi 4B. Everything went smoothly as I followed the guide for Raspi installation. However after I logged in to UI and went to System->OMV-Extras --- tick box --- > Extras repo ---click ---> Save.


    When the Save action is running I get an error:



    Can anybody please help me out to debug that one in order to fix it? I will be grateful for any hints.

    EDIT:

    Oh, and before I run the `apt full-upgrade with the following output:


    EDIT2:


    I just uninstalled OMV-Extras using System->Plugins and the errors seems to go away.