Question about what to put on RAID and what to put on NVME

[ch00f@lemmy.world]

So are you thinking like a raspberry pi with an 18TB hard drive accepting nightly backups through restic?

[ch00f@lemmy.world]

Doesn't this just pass the issue to when the snapshot is made? If the snapshot is created mid-database update, won't you have the same problem?

[ch00f@lemmy.world]

Wouldn't this require the service to go down for a few minutes every night?

[schizo@forum.uncomfortable.business]

Make sure, if you use hardware RAID, you know what happens if your controller dies.

Is the data in a format you can access it easily? Do you need a specific raid controller to be able to read it in the future? How are you going to get a new controller if you need it?

That's a big reason why people nudge you to software raid: if you're using md and doing a mirror, then that'll work on any damn drive controller on earth that linux can talk to, and you don't need to worry about how you're getting your data back if a controller dies on you.

[bizdelnick@lemmy.ml]

I meant software RAID of course. Hardware RAIDs just cause headacehes, but fake RAIDs that are built into motherboards are a real nightmare.

[malreynolds@slrpnk.net]

Yup (although minutes seems long and depending on usage weekly might be fine). You can also combine it with updates which require going down anyway.

[ch00f@lemmy.world]

So I’m kind of on the fence about this. I ran a raid boot disk system like 12 years ago, and it was a total pain in the ass. Just getting it to boot after an update was a bit hit or miss.

Right now I’m leaning towards hardware nvme raid for the boot disk just to obfuscate that for Linux, but still treat it delicately and back up anything of importance nightly to a proper software raid and ultimately to another medium as well.

[blackstrat@lemmy.fwgx.uk]

Sounds like a good plan to me

[suzune@ani.social]

2 HDDs (mirrored zpool), 1 SATA SSD for cache, 32 GB RAM

First read: 120 MB/s
Read while fully cached (obviously in RAM): 4.7 GB/s

[killabeezio@lemm.ee]

1. You don't need zfs cache. Stay away from it. This isn't going to help with what you want to do anyway. Just have enough RAM.

2. You need to backup your stuff. Follow the 3-2-1 rule. RAID is not a backup.

3. Don't use hardware raids, there are many benefits to using software these days.

With that said, let's dig into it. You don't really need NVMe drives tbh. SATA is probably going to be sufficient enough here. With that said, having mirrored drives will be sufficient enough as long as you are backing up your data. This also depends on how much space you will need.

I just finished building out my backup and storage solution and ended up wanting NVMe drives for certain services that run. I just grabbed a few 1 TB drives and mirrors them. Works great and I do get better performance, even with other bottlenecks. This is then replicated to another server for backup and also to cloud backup.

You also haven't said what hardware you are currently using or if you are using any software for the raid. Are you currently using zfs? Unraid? What hardware do you have? You might be able to use a pice slot to install multiple NVMe drives in the same slot. This requires bifurcation though.

[ataridump@lemmy.world]

The basic concept of the 3-2-1 backup strategy is that three copies of the data are made to be protected, the copies are stored on two different types of storage media and one copy of the data is sent offsite