pi 4 help regarding usb raid

  • I installed open media but was kind of dissapointed to find i cant have raid 1 on usb so my question is can i do soemthing else add on or plugin which mirrors one drive,i have about 5tb of data i cant afford to leave to chance.

  • Are there any guides to this im new to open media vault

    https://drive.google.com/file/…WuyhixAc/view?usp=sharing


    That's a pic of my current setup. It's really quite simple.. the hardest thing is the scheduling is a little awkward if it's not set up properly. The easiest way is to set up your "working drive", and it will be your "source". Have all your media, files, etc.. in folders under 1 folder. The "target" is the "backup". I don't put that drive in any services at all, other than rsync, so data cannot accidentally be deleted from there by users over SMB, NFS, etc. Then schedule the job. In the example above... That job runs every day at 0900. if I wanted it to run say, every 9 hours.. then I would set it exactly as above, and enable the "N" trigger next to the hour


    Couple caveats on scheduling. If as above, it's set to 9, and the "minutes" was set to 15... then every day at 0900, the job would run over and over for 15 minutes. If the N trigger was enabled on 0900 and 15, then it would run once, at 0915. If you have it set to to 9, and the "minutes" to *.. then every day at 9, at the top of the hour it is going to run over and over for 60min. Thus why my Minutes is set to "0", as I want it to run once at the top of the hour, and that's it. I've never messed with the days/weeks much as I prefer my drive back up daily, but I'm sure it operates similarly.


    It's not in the pic, but at the bottom you'll see the "delete" trigger.. I personally leave that off. Basically if anything on the source is deleted, when the job runs again, it will also be deleted from the "backup". By leaving it off, it is not deleted from the backup. This is nice so if I find I've accidentally deleted a file, etc.. I can just SSH in my server, go to my backup drive, and copy it back to the source via command line. Every couple of weeks, I usually log in, enable the delete trigger, run the job manually to bring the drives completely in sync, then turn it off again.


    Hope that helps.

  • When you are comfortable with this you might want to have a look at rsnapshot. It is based on rsync, but creates snapshots. So you are able to go back in time and restore previous versions.

    I didn't think rsnapshot did local backups, only remote. Might have to check it again

  • Another way to do the same backup using Rsync is through Scheduled Tasks using the following command:

    rsync -av --delete /srv/dev-disk-by-label-SOURCE/ /srv/dev-disk-by-label-DESTINATION/

    This method allows you to have multiple shares in your SOURCE drive (again, none in the backup or DESTINATION drive.) As in KM0201 ’s version you can leave off the delete variable until you are comfortable with the process.

    (From crashtest ’s Getting Started with Openmediavault 5 beginning on page 59.)

    Simple and sure backup and restore: In a Scheduled Job: rsync -av --delete /srv/dev-disk-by-label-SOURCE/ /srv/dev-disk-by-label-DESTINATION/ (HT: Getting Started with OMV5)
    OMV Version: Ver. 5 (current) - Hardware: NanoPi M4, Nextcloud, Plex, Airsonic, Booksonic, Calibre, & Heimdall - Acer Aspire T180, backup - Odroid XU4, Pi-Hole (DietPi) - Testing/Playing: hc2, xu4, Pi 3B+, Odroid H2, and HP dx2400, Debian 10 XFCE.

Participate now!

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