Motherboard Recommendation

I'll second chente 's statement on RAID. If you're looking at RAID1, rsync'ing two disks would be a better choice. You'd have true backup.

Zitat von crashtest

I'll second chente 's statement on RAID. If you're looking at RAID1, rsync two disks would be a better choice. You'd have true backup.

Agree.. for the average home user... Raid 1 is almost useless and just using rsync is a better solution. It's less headache, is an actual second copy. no trying to recover and rebuild raids if something fails... just pop in a new drive and rsync the data to the new drive.

Zitat von KM0201

no trying to recover and rebuild raids if something fails... just pop in a new drive and rsync the data to the new drive.

And,,, it's possible (actually easy) to redirect shares to the Rsync'ed backup drive. If redirected at the shared folder level, top level services follow (Samba shares, etc.). That gives access to the users data while waiting for a new drive to arrive. It's real backup and recovery is quick.

Zitat von crashtest

And,,, it's possible (actually easy) to redirect shares to the Rsync'ed backup drive. If redirected at the shared folder level, top level services follow (Samba shares, etc.). That gives access to the users data while waiting for a new drive to arrive. It's real backup and recovery is quick.

Yup.

How I've done it for...a long, long time... is Drive A, is basically for all my services, nfs, docker, etc., Drive B, is just a backup. It isn't available to anything but rsync. In the event Drive A fails (which thankfully only happened once)... you can move Drive B into place pretty easily until the new drive arrives... or just shut down until the new drive arrives (2 is 1, 1 is none, you know).

Here in the US, most stuff can pretty much be ordered very close to overnight.... so at least for me, it wouldn't be a big deal my server being down for a day.

Zitat von KM0201

Here in the US, most stuff can pretty much be ordered very close to overnight.... so at least for me, it wouldn't be a big deal my server being down for a day.

I have a full backup server, complete with identical shares, users and permissions. In the event of the failure of the primary, I activate SMB on the backup server and it appears on the network, exactly like the primary but with a different hostname. (That's a bit extreme for home use but I like good backup. )

Zitat von crashtest

I have a full backup server, complete with identical shares, users and permissions. In the event of the failure of the primary, I activate SMB on the backup server and it appears on the network, exactly like the primary but with a different hostname. (That's a bit extreme for home use but I like good backup. )

I have a remote backup server as well..lol. It's actually next on the upgrade list. It's an old HC2 with OMV 5 on it. I've not even tried to upgrade it as I don't think armbian is available for it. It's pretty well stuffed to the gills. I'm thinking I'll buy the rockpro64 NAS kit, and throw an 8 and 4tb drive in it, just like my server.

Zitat von roko772

Thank you, I'll definitely consider that!

In Poland it's also not a problem to buy new HDD with door-to-door delivery within few days.

It does have the added benefit, if you leave the delete trigger off (I do).. and you accidentally delete something and don't realize it for a couple of days... even if the job has already ran, it's still going to be on the "backup" (on a mirror, it would be gone unless you had it backed up elsewhere). In this instance, which has also happened to me.. just SSH the server, cd to your "Backup" drive, and copy the file in question back to the "main" drive.

For me, usually around once a month, I'll log in and enable the delete trigger, and then run the job manually to bring the two drives 100% in sync. Once it's done, I disable it again. How often it runs, is up to you... Mine runs daily about 4am, as I'm usually at work at that time. Then every Sunday at 5am, a script runs to update my server, then at 6am, a script runs to image my drive OS drive and put the image on my data drive.

For me, it's pretty much a "set it and forget it" process that took me a while to come up with exactly how I wanted to do it.. TOnce a month or so I log in and run my rsync job with the delete trigger and then i check the folder with my OS disk images, and delete all but the 2 most current.

Zitat von KM0201

I have a remote backup server as well..lol. It's actually next on the upgrade list. It's an old HC2 with OMV 5 on it. I've not even tried to upgrade it as I don't think armbian is available for it.

It is. Mine is upgraded to OMV6. But you could also do a fresh install:

https://www.armbian.com/odroid-xu4/

Zitat von macom

It is. Mine is upgraded to OMV6. But you could also do a fresh install:

https://www.armbian.com/odroid-xu4/

Oh I would just do a clean install.

In that case, I might just buy a 2bay USB enclosure. I don't need amazing speed. All it does is run syncthing.

I honestly don't concern myself with power usage. My server stays on really close to 24/7, and it's not making enough of a difference I notice.