Help Identifying fsarchiver Backup and Restore Approach (Backup Plugin)

  • Hi everyone,


    I'm trying to understand/document the inner workings of the OpenMediaVault Backup Plugin, specifically how the fsarchiver tool is used for restoring system backups.


    I came across this helpful guide. Based on this, I've created a few diagrams representing different approaches for fsarchiver method, so that I understand what's beeing backup and what will be restored:


    Option 1:

    • Backup OS drive + OMV (config, installed plugins and their config).
    • Mergerfs with its settings and drives content


    Option 2:

    • Backup OS drive + OMV (config, installed plugins and their config).


    Option 3:

    • Backup OS drive + OMV (config, installed plugins and their config).
    • Backup Docker containers, their settings and volumes


    Option 4:

    • Actually no diagram, but: backup captures the entire system (Options 1 thru 3)

    Option 5:

    • None of the above is right


    Can someone with expertise in the OMV Backup Plugin confirm which of these architectures represent the approach used by fsarchiver for restoring backups?


    Thanks in advance for your help!

    • New
    • Official Post

    Normally option 2 (depends on how you install OMV) unless you leave docker storage in the compose plugin in /var/lib/docker. The plugin is meant to backup the OS which has the OMV database and plugin config files.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • unless you leave docker storage in the compose plugin in /var/lib/docker.

    You mean this?


    BTW, looks like when I upgraded to OMV 7 (from OMV 6), that setting got changed and I need to move that directory to the Mergerfs main pool, not the main OS disk which is small. Should I shutdown Docker, move the folder, change the setting and re-start?

    • New
    • Official Post

    ou mean this?

    yep.


    BTW, looks like when I upgraded to OMV 7 (from OMV 6), that setting got changed

    It shouldn't have been changed by the upgrade.


    need to move that directory to the Mergerfs main pool,

    You shouldn't put docker storage on mergerfs. Volumes are fine though.

    Should I shutdown Docker, move the folder, change the setting and re-start?

    If it was running on a different folder previously, you should just be able to change back to the original path.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New
    • Official Post

    That should be ok.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!