Hello everyone, first post here, feeling a bit shy .
I had my first contact with OMV a few months ago, have been reading and learning so far. I was able to deploy around 15 containers using openmediavault-compose, including nginx-proxy-manager to access some of the services from the outside.
I though it would be now a good idea to start backing-up the whole docker ecosystem. So I referred back to the guide I used at the beginning to install and config everything (here) but I wasn't able to find much information about how to do it. Only the section backup_appdata folder throws a couple of comments there and I find my self with a few question marks. Of course I tried to research the forum and googled and so on... but I got lost in a ocean of rsyncs, Rsnapshots, cron jobs....etc.
I better ask before moving on. Using the build-in functionality of the omv-compose plugin seems convenient since, as far as I understood, it can stop the containers, synchronise the files..etc and get configured with-in the GUI itself.
My questions are:
- is it a good idea to use such feature or should I go down another path?
- what exactly does the omv-compose backup plugin functionality back-up? I though it was only going to be the compose files but after running it manually I saw the folder getting filed up with lots of stuff (in a way I can't understand)
- When choosing to back-up the system weekly It seems I can't specify when do I want to do it. Does the feature decide by it self?
If someone could help me please understand a bit further how it works or maybe pointing me to a more extensive documentation would be sufficient.
PS: I know the backing strategy might depend a lot on what kind of containers do I run. I can specify them if needed.
Thank you very much