Backing up unionfs pool to external drives

  • Hello,

    Following Techno Dad Life's guides on Youtube, I was able to install OMV under Proxmox. I was also able to easily create a unionfs + snapraid pool of 4 x 10tb drives. 2 for data, 2 for parity, all under OMV. The drives will be used solely for media and long-term seeding (I have qbtorrent using VPN installed in a docker, also thanks to TDL). I have two additional 10tb drives in an external 2-bay enclosure. My goal is to plug in my external drives, backup my unionfs pool (though rsync i guess?) and unmount; and possibly access that pool in another computer if necessary. I intend to have the backup offline. I have a few questions:


    1- Is there a way through the OMV GUI to mount and unmount a unionfs pool? Or better yet why can't I unmount the pool under 'File Systems' (the button is grayed out)?

    2- Is rsync the most effective way currently in OMV to backup to ? USB Backup is another option.

    3- Would I need an install of mergerfs/unionfs in any machine I want to access my external pool?

    4- What alternatives would you recommend in OMV?


    If this isn't feasible, I was thinking to create another instance of OMV under Proxmox, route the usb port that I use to connect the external drives, create a network share + remote mount on the first OMV, use duplicati and only turn that VM on when backing up. And I guess access the files through a network share?


    I know this is a long post. I have looked here, reddit, etc. and read the respective docs for each tool and haven't found what I need for my needs. I appreciate any answers/suggestions. Thank you!

  • 1. You can't unmount the filesystem because it is used by some service. Possibly smb share?


    2. Rsync is a sync tool. This means that it can very efficiently update a copy of a filesystem to match the original, as long as there are few differences. Perhaps a few new files added and some deleted. But most the same. Rsync will do the minimum possible to make the copy identical to the changed original.


    This means that rsync is very inefficient if there are big changes between backups. And the first time you do a backup.


    Rsync can ALSO be used to create versioned snapshots of the original. It can use hardlinks to avoid having to store a file more than once, but the hardlink to that file can appear in many snapshots and take up very little storage.


    This means that you can have one snapshot that looks just like the original as it was yesterday. And one as it was last week or last month. And so on.


    I use rsync in scripts to make versioned snapshots of folders like this. And also delete old snapshots. Typically I keep 7 daily snapshots, 4 weekly and 3-12 monthly. The rsnapshot plugin for OMV works in a similar way.


    3. That depends on how you use the two backup HDDs. If you use them as a mergerfs filesystem during a backup, then it may be easiest to use them the same way to access the backup. It is not necessary, but then you don't have to search on two HDDs for a file.


    You can also backup your original filesystem in several parts. Depending on how you are organized. For instance "cold" data that rarely changes only need to be backed up when it changes. For instance finished TV series/seasons and old movies. Folders that are frequently updated with new "hot" files often need to be backed up more frequently. For instance ongoing TV series and new movies. Or files that need renaming and metadata.


    Perhaps a few times per year you migrate stuff from the "hot" side to the "cold". When metadata is perfect and/or the TV series season is over. And you update the "cold" manual backups.


    But you really shouldn't need to access the external backups on some other system. Access the originals using the network. It is a NAS after all.


    4. I would ignore snapraid and instead go for good backups. And split the data in "hot" (=changing often) and "cold" (=mostly static). Or have snapraid with just one parity drive.


    I would use two drives for a pooled mergerfs filesystem shared by OMV. One or two drives, possibly also as a pooled mergerfs filesystem in the same NAS, but only for automatic frequent versioned rsync snapshots. Mainly for "hot" files, but also extra backup of valuable "cold" files. Family photos, for example. And two external drives for mainly "cold" manual versioned snapshots. Also valuable "hot" files. But updated only a few times per year, when "hot" files are moved to the "cold" side.


    This is almost how I do it today, but between several separate NAS over the network, typically not using mergerfs but SBCs with big (12TB-16TB) single HDDs. Using scripts to make automatic versioned snapshots of folders.

    Be smart - be lazy. Clone your rootfs.
    OMV 5: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

Participate now!

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