Configuring OpenMediaVault for a Selfhosting Environment (part 2)
ฝัง
- เผยแพร่เมื่อ 5 ก.ค. 2024
- 0:00 - Intro
0:39 - SSH Client Configuration
2:48 - Update from terminal
3:25 - Timeshift
10:04 - Shared Folders
12:22 - Home Folder
13:47 - Alias Update to Snapshot Before Updating
15:58 - Setting Up Symlinks for Easier Navigation
19:27 - Samba Shares
24:36 - Outro - วิทยาศาสตร์และเทคโนโลยี
![[TH] VCT Pacific Stage 2 - Week 4 Day 1 // PRX vs RRQ | GE vs GEN](http://i.ytimg.com/vi/iIi2_04jGr0/mqdefault.jpg)
Good work, great series
Thanks for the great Tutorial
Great stuff. Thanks
Really useful, thank so much for the tutorial. Recently the OMV 7 everytime reboot will stopped and have a message " watchdog did not stop", how to get rif of this? thx
About Timeshift and snapshot before update. Today I learned using method from video ssh way works great but if you try to update from user interface timeshift dont create snapshot before updates.
That's correct, setting an alias in bashrc won't have any effect on the UI update process. You can choose which way to run it. I usually prefer SSH sessions for most work on the server including updates. The UI is nice for setting up certain things, but it's a bit clunky and less efficient compared to a terminal session.
I set keyboard shortcut on my desktop (XFCE), alt+enter, which opens a terminal for me. Then type 'ssh omv' to connect to the server then 'update' and find that is faster then opening a browser, going to OMV, logging in, and running the update process. In this way I can have an update running on a server faster than I can even open a browser. A great thing about Linux desktop is the ability to customize it in this way, fully customized keyboard shortcuts where your fingers rarely have to leave your keyboard to navigate and control your computer.
Awesome tutorial as always! Question: For now I only have the OS ssd (which came with the mini PC). Before my data drives arrive, it seems I cannot create the home folder on the OS drive. Is there a way around it? Or is this not recommended?
Thank you! It isn't recommended but there is a way around it, if you look in the OMV plugins there is a plugin called sharerootfs and that will allow you to create shares on the OS drive. I think it would be okay to put your home folder on it just remember to back it up when you setup your backups. Thanks for waching, :).
@ysoon_ Yes, I guess I'm still thinking how to setup this: me coming from a raspberry pi with some SSDs attached and functioning as a "NAS" where all the "data" was on the external SSDs and the home folder and apps including docker are installed on the OS drive. Since I've bought the mini PC with a 500 GB drive I thought that I can use that for the OS and dockers and use timeshift on it + back it up in case the drive fails. But I didn't think about home folders because I wasn't storing anything in the home folder of the raspberry pi :) When I have the data drives, my plan is to create a "family" user on them for family photos and separate users later as needed.
On your setup are the docker containers on a data drive?
I will probably wait to have the complete new system with data drives and then watch again your videos in order. That's what I like: you explain everything and you are picky (just like I am :D )
I do hope you get a lot more subscribers as your videos are worth it :) Thanks again!
Very nice, I started off on a Pi too, :). Personally, I wouldn't put any data on the OS drive. Also note timeshift by default won't backup home folders. It is only meant to take snapshots of the OS itself, and not of any of the user data or any other data. Now you can make it do that, but it's not what it is intended to be doing. In fact, you want to explicitly exclude your data and data drives from it. For making backups of your data you will want to use something like borg or restic. So... I would recommend to only install the OS to that drive and use timeshift on it to take snapshots in case something breaks then you can easily boot back into a known working condition.
Then on your data drive or data drive pool (if you are combining multiple drives) you can have a directory structure to organize things. So let's say your data drive is mounted at \srv\%yourdriveuid%\ then you could have a directory structure which looks like \srv\%yourdriveuid%\docker\immich \srv\%yourdriveuid%\docker\airsonic and all your docker compose files and data is organized and bind mounted there to easily back up with your backup solution (borg or restic). Then you can have other folders like \srv\%yourdriveuid%\media \srv\%yourdriveuid%\media\movies \srv\%yourdriveuid%\media\pictures. Your \srv\%yourdriveuid%\home. You can have backups for other devices \srv\%yourdriveuid%\backups\user1\phone etc. I also have a \srv\%yourdriveuid%\common folder and in that folder I have my Pictures, Downloads, Documents, etc. where my other computers link to in their own \home\user folders and also in Windows to link in my user folder. And you can create symlinks to make those locations more easily accessible and addressable, I show how I do that in /shared folder in one of my videos.
You can manage who can access what in your family with user/file permissions and share things with SAMBA or use specific apps and services like immich and jellyfin and airsonic, many of which also support user permissions.
One more thing, you want all of your data on your one data drive or data drive pool, but then you still want another drive for creating a borg repo on and backing up all the data from the first data drive to the second data drive that has the borg repo. You have to use a proper backup tool like borg or restic and you have to backup to a seperate device in order to make a proper backup. So you want a minimum of 3 drives: one for the OS, one for your data, one for creating backups. Hopefully I didn't ramble too long and confuse you on anything. Your comments are kind, thank you very much!
@@somedaysoon33 For now, I only have one SSD from the PI which was no longer powered by the PI (that's why I moved to a mini PC). I did bought a usb-c 10GBit enclosure to use with the mini PC but for this month the budget for "toys" is empty so I have to wait for the next month to buy the HDDs. Until then, I mounted the SSD on OMV, created and shared the entire drive using SMB :) and it worked from the start even though the drive is NTFS. My plan is to move all the data from the SSDs to the new drives (probably 3*18 TB for now): 1 for photos / videos etc only, 1 for movies, shows and docker and 1 for parity (SnapRAID). So do you recommend Borg instead of SnapRAID? To basically have only 2 drives then? 1 for data and 1 for backup? The USB enclosure has 5 slots but I don't think I need all of them initially :).
Also, if the OS breaks down, saving the docker on a separate drive will make it more easy to redeploy them on a new OS drive?
Now for sure I did ramble too long :D
You can use both SnapRAID and borg, that's what I do, but if you only use one then you should use borg because SnapRAID is not a proper backup solution. It's a mix-in-between RAID and a backup, but it's not quite either. The reason it is not a backup is because it does nothing to protect against accidental file deletions. Let's say you or another user mistakenly deletes a bunch of files... well... SnapRAID is going to sync those deletions and then those files are gone forever. If you've ever heard the expression, "RAID is not a backup," that's the reason. However, if you have proper backups with a true backup solution like borg, then you can restore those deleted files. SnapRAID is great because you can easily have drive parity, across multiple drives, and restore drives if they fail... but you don't want to count on it as your backup solution. Borg is also better for backups because it supports encryption, compression, and file deduplication and other nice features like sending to remote locations.
Yeah, you got it, if the OS drive fails or you need to reinstall the OS then it is much better for your docker data to be on a different drive. You can easily re-install the OS, even a completely different OS or distro and spin the containers back up right were you left them.
You could do 1 drive for all the data, 1 drive for SnapRAID parity, 1 drive for borg repo. Or if you want to use 2 drives for your data then I would say use the 3rd drive for a borg repo instead of a SnapRAID parity drive because a proper backup system is more important than having drive parity. Then down the road if you want to add a 4th drive to use SnapRAID you can, because you can always do it later. I would probably go that route, and worry about SnapRAID later.
i keep getting an error when i try to create a snapshot
E: rsync returned an error
E: Failed to create new snapshot
Failed to create snapshot
Not sure where i screwed after following your steps
Based on a quick search it's likely you have an incompatible version of rsync installed and you would need to install the correct version that timeshift wants.
@@somedaysoon33thanks for the reply. I tried tinkering around with rsync and timeshift. i decided to do without timeshift. maybe i'll find an alternative. But thanks for making these videos. They are very informative and helpful.
I installed timeshift, but when I run the --create it tries to backup /sda but my system drive is /sdd. Not sure why it's not backing up the system drive. Ideas?
What does your timeshift.json file look like?
@@somedaysoon33 the config file doesn't have an option to specify system drive. only the device to backup to. and sda is an ssd that I don't want to use. i know timeshift should be easy but OMV has been such a stressful disaster for years. nothing but constant errors left and right, stuff that breaks or doesn't work, and just plain unreliable. so many times i've woken up to a server that is unreachable with a zillion errors onscreen with no way to login. not sure there's another option is my case, however.
@@KenInJapan81 Your experience with OMV has not been mine whatsoever. I have ran it for the past 8 years on multiple variations of hardware without any problems. I'm currently running it on 3 different servers and I run a ton of services. Where is your / root mounted? Because timeshift should just be using that to backup and it doesn't matter what drive it's mounted on. You could always go into your timeshift.json and put an include on / root, exclude the other drive and run it that way. But again, I don't understand why it would be backing up any drive unless you have root mounted on it.
@@somedaysoon33 Maybe your hardware plays nice more than mine does. I've been using OMV for years on 3+ devices. I think most of the problems relate to using the GUI, and if you're great with the CLI you will have a better experience. I don't know if I
ve gotten better or if OMV has gotten better but I do seem to be having less problems as time goes on. Thanks for replying.
How long does it take for timeshift to create the initial snapshot for you? Maybe it just takes a while and isn't hanging for me. My OMV system is on a fast USB drive, but the port is slow so maybe that's a bottleneck? There is a new timeshift OMV plugin, but I have the same problem as installing/running via CLI. /root is at /sdd and sda is an SSD that I'll be using for docker eventually but is currently empty.
@@KenInJapan81 Hmm, I''ve never timed it but I would venture to guess ~20-30 minutes. Yeah, that could be a bottleneck but I've ran it on some slow hardware like rock64 and Pi3 previously when I was first starting. I would make sure to exclude any other data drives or your sdd docker drive from timeshift, I think I showed how to do it. Find out where it is mounted and make an exclusion for it. I always exclude the home directories and other data drives from timeshift so in omv that's usually anything under /srv/ and then also /root/ and /home/ and since I put symlinks in /shared/ I also exclude that too.