I was wondering whether you have found solution? I am running into same problem
I have definetly ran out of ideas.
I was wondering whether you have found solution? I am running into same problem
I have definetly ran out of ideas.
I see. I suppose if I run the backup at night when there are no changes to the data volumes it should be safe. I might have overcomplicated things. Thanks for your time!
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.
QuoteNow syslog shows:
Code
CodeDec 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.
All is clear now. Thanks for your time. I will follow github issue you referenced.
Nice find! But what is that extra repo in the end? Why would I need that? Or I should not care about it as stated per guide (as geaves has mentioned) that its not for SBC users.
QuoteYou 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.
$ sudo apt-get update
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives Release
Ign:2 file:/var/cache/openmediavault/archives Release
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages [1074 B]
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Hit:5 http://packages.openmediavault.org/public usul InRelease
Hit:6 http://archive.raspberrypi.org/debian buster InRelease
Hit:7 https://download.docker.com/linux/debian buster InRelease
Get:8 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:9 http://httpredir.debian.org/debian buster-backports InRelease [46.7 kB]
Hit:10 https://openmediavault-plugin-developers.github.io/packages/debian usul InRelease
Hit:11 https://openmediavault.github.io/packages usul InRelease
Hit:12 https://openmediavault-plugin-developers.github.io/packages/debian usul-extras InRelease
Get:13 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Fetched 13.1 MB in 8s (1574 kB/s)
Reading package lists... Done
Display More
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:
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
openmediavault-omvextrasorg
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/67.1 kB of archives.
After this operation, 591 kB of additional disk space will be used.
Get:1 file:/var/cache/openmediavault/archives openmediavault-omvextrasorg 5.6 [67.1 kB]
Selecting previously unselected package openmediavault-omvextrasorg.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 61609 files and directories currently installed.)
Preparing to unpack .../openmediavault-omvextrasorg_latest_all5.deb ...
Unpacking openmediavault-omvextrasorg (5.6) ...
Setting up openmediavault-omvextrasorg (5.6) ...
Updating configuration database ...
raspberrypi:
----------
ID: omvextrasbaserepo
Function: pkgrepo.managed
Name: deb https://openmediavault-plugin-developers.github.io/packages/debian usul main
Result: True
Comment: Configured package repo 'deb https://openmediavault-plugin-developers.github.io/packages/debian usul main'
Started: 22:51:38.655228
Duration: 19578.577 ms
Changes:
----------
repo:
deb https://openmediavault-plugin-developers.github.io/packages/debian usul main
----------
ID: deb https://openmediavault-plugin-developers.github.io/packages/debian usul-testing main
Function: pkgrepo.absent
Result: True
Comment: Package repo deb https://openmediavault-plugin-developers.github.io/packages/debian usul-testing main is absent
Started: 22:51:58.234421
Duration: 203.744 ms
Changes:
----------
ID: deb https://openmediavault-plugin-developers.github.io/packages/debian usul-extras main
Function: pkgrepo.absent
Result: True
Comment: Package repo deb https://openmediavault-plugin-developers.github.io/packages/debian usul-extras main is absent
Started: 22:51:58.438568
Duration: 121.604 ms
Changes:
----------
ID: deb [arch=armhf] https://download.docker.com/linux/debian buster stable
Function: pkgrepo.managed
Result: True
Comment: Configured package repo 'deb [arch=armhf] https://download.docker.com/linux/debian buster stable'
Started: 22:51:58.560571
Duration: 20617.147 ms
Changes:
----------
repo:
deb [arch=armhf] https://download.docker.com/linux/debian buster stable
----------
ID: deb http://linux.teamviewer.com/deb stable main
Function: pkgrepo.absent
Result: True
Comment: Package repo deb http://linux.teamviewer.com/deb stable main is absent
Started: 22:52:19.178380
Duration: 129.924 ms
Changes:
----------
ID: configure_apt_pref_omvextras
Function: file.managed
Name: /etc/apt/preferences.d/omvextras.pref
Result: True
Comment: File /etc/apt/preferences.d/omvextras.pref updated
Started: 22:52:19.316284
Duration: 255.138 ms
Changes:
----------
diff:
New file
mode:
0644
----------
ID: refresh_database_apt
Function: module.run
Name: pkg.refresh_db
Result: False
Comment: No function provided.
Started: 22:52:19.573533
Duration: 1.999 ms
Changes:
Summary for raspberrypi
------------
Succeeded: 6 (changed=3)
Failed: 1
------------
Total states run: 7
Total run time: 40.908 s
Processing triggers for openmediavault (5.6.5-1) ...
Updating locale files ...
Updating file permissions ...
Purging internal cache ...
Restarting engine daemon ...
Done ...
Display More
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:
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color omvextras 2>&1' with exit code '1': raspberrypi:
----------
ID: omvextrasbaserepo
Function: pkgrepo.managed
Name: deb https://openmediavault-plugin-developers.github.io/packages/debian usul main
Result: True
Comment: Package repo 'deb https://openmediavault-plugin-developers.github.io/packages/debian usul main' already configured
Started: 22:35:47.805016
Duration: 268.127 ms
Changes:
----------
ID: deb https://openmediavault-plugin-developers.github.io/packages/debian usul-testing main
Function: pkgrepo.absent
Result: True
Comment: Package repo deb https://openmediavault-plugin-developers.github.io/packages/debian usul-testing main is absent
Started: 22:35:48.073545
Duration: 124.08 ms
Changes:
----------
ID: deb https://openmediavault-plugin-developers.github.io/packages/debian usul-extras main
Function: pkgrepo.managed
Result: True
Comment: Configured package repo 'deb https://openmediavault-plugin-developers.github.io/packages/debian usul-extras main'
Started: 22:35:48.198021
Duration: 16686.614 ms
Changes:
----------
repo:
deb https://openmediavault-plugin-developers.github.io/packages/debian usul-extras main
----------
ID: deb [arch=armhf] https://download.docker.com/linux/debian buster stable
Function: pkgrepo.managed
Result: True
Comment: Package repo 'deb [arch=armhf] https://download.docker.com/linux/debian buster stable' already configured
Started: 22:36:04.885201
Duration: 268.28 ms
Changes:
----------
ID: deb http://linux.teamviewer.com/deb stable main
Function: pkgrepo.absent
Result: True
Comment: Package repo deb http://linux.teamviewer.com/deb stable main is absent
Started: 22:36:05.153881
Duration: 135.422 ms
Changes:
----------
ID: configure_apt_pref_omvextras
Function: file.managed
Name: /etc/apt/preferences.d/omvextras.pref
Result: True
Comment: File /etc/apt/preferences.d/omvextras.pref is in the correct state
Started: 22:36:05.295737
Duration: 136.533 ms
Changes:
----------
ID: refresh_database_apt
Function: module.run
Name: pkg.refresh_db
Result: False
Comment: No function provided.
Started: 22:36:05.434354
Duration: 1.669 ms
Changes:
Summary for raspberrypi
------------
Succeeded: 6 (changed=1)
Failed: 1
------------
Total states run: 7
Total run time: 17.621 s in /usr/share/php/openmediavault/system/process.inc:195
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/openmediavault/engined/rpc/omvextras.inc(81): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)
#6 [internal function]: OMVRpcServiceOmvExtras->setSettings(Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setSettings', Array, Array)
#9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('OmvExtras', 'setSettings', Array, Array, 1)
#10 {main}
Display More
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:
The following packages will be upgraded:
apt apt-utils libapt-inst2.0 libapt-pkg5.0 monit wpasupplicant
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4,126 kB of archives.
After this operation, 55.3 kB disk space will be freed.
Do you want to continue? [Y/n] y
Reading changelogs... Done
(Reading database ... 61688 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.8.2.3_armhf.deb ...
Unpacking libapt-pkg5.0:armhf (1.8.2.3) over (1.8.2.2) ...
Setting up libapt-pkg5.0:armhf (1.8.2.3) ...
(Reading database ... 61688 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.8.2.3_armhf.deb ...
Unpacking libapt-inst2.0:armhf (1.8.2.3) over (1.8.2.2) ...
Preparing to unpack .../archives/apt_1.8.2.3_armhf.deb ...
Unpacking apt (1.8.2.3) over (1.8.2.2) ...
Setting up apt (1.8.2.3) ...
(Reading database ... 61688 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.8.2.3_armhf.deb ...
Unpacking apt-utils (1.8.2.3) over (1.8.2.2) ...
Preparing to unpack .../monit_1%3a5.26.0-1_armhf.deb ...
Unpacking monit (1:5.26.0-1) over (1:5.25.2-3) ...
Preparing to unpack .../wpasupplicant_2%3a2.7+git20190128+0c1e29f-6+deb10u3_armhf.deb ...
Unpacking wpasupplicant (2:2.7+git20190128+0c1e29f-6+deb10u3) over (2:2.7+git20190128+0c1e29f-6+deb10u2) ...
Setting up monit (1:5.26.0-1) ...
Configuration file '/etc/monit/monitrc'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** monitrc (Y/I/N/O/D/Z) [default=N] ? N
Setting up libapt-inst2.0:armhf (1.8.2.3) ...
Setting up wpasupplicant (2:2.7+git20190128+0c1e29f-6+deb10u3) ...
Setting up apt-utils (1.8.2.3) ...
Processing triggers for systemd (241-7~deb10u7+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
W: Operation was interrupted before it could finish
Display More
EDIT2:
I just uninstalled OMV-Extras using System->Plugins and the errors seems to go away.