It depends how valuable your data is, what backup strategy you have, and how long you’re prepared to wait to get access to your data when a drive fails.
Personally if/when I migrate my main dataset to SSD, I’ll stick with RAIDZ2/RAID6.
SSD’s are cheap nowadays. They’re also much more reliable than HDD’s. That said, when they fail it’s usually catastrophic failure with total data loss.
If your data that’s important to you, I would still use redundant storage. Especially since the cost is minimal.
The cheaper SSDs can be very failure-prone though. I actually use second-hand spinning disks in my server and I have a whole bunch of spares waiting in the wings. I am still backed up though.
As someone else has pointed out, it really depends on your use case. Although I personally keep my drives (SSD & HDD) in a redundant RAID configuration as my data is largely mission-critical.
At least with spinners you often get enough advanced warning of impending doom via SMART. Critical stuff I am still keeping on spinning disks backed up to tape and a privacy-respecting cloud service.
In my opinion the most important thing to have is an off-site backup. If you have achvieved that, it’s only a matter of how long you are willing to wait for the recovery.
If your answer is something like “it cannot wait” then you should go with at least raid 1 and consider additional meausres for the event when your whole array fails.
Maybe as a side note: a mirror raid does not only provide data redundancy but also improves read speeds. For SATA limited SSDs this can be interesting.
SATA SSDs don’t really make sense nowadays anymore. Last time I checked, they cost the same and are actually the exact same thing, except SATA SSDs have a big, mostly empty, plastic case around them and use a slow connector
How, with a couple of hba I can connect connect easily dozens of sata SSDs to a consumer motherboard, while doing the same with nvme drives not exactly as easy or cheap
I’m quite disappointed by most comments so far talking about RAID and data loss. That is not what RAID is for at all.
RAID is for uptime/availability. When a drive fails, the system will keep running and working. For companies, that would lose thousands of currency per hour with a downtime, this is super important that the system keeps running. At home, it’s convenience that you can order a new drive and replace without hours of setting up and copying before you can watch the next episode again.
Backups are against data loss. If a single drive fails, a RAID fails or you get some encryption malware or an employee destroys stuff on purpose, then everything is destroyed. It doesn’t matter if it was a single, any RAID, HDD or SSD. You order a new drive, make a new volume and restore the data from your backup.
Well, more specifically it is protecting against a specific form of data loss, which is hardware failure. A good practice if you’re able is to have RAID and an offsite/cloud backup solution.
But if you don’t, don’t feel terrible. When the OVH datacentre had a fire, I lost my server there. But so did a lot of businesses. You’d be amazed at how many had no backup and were demanding that OVH somehow pry their smouldering drives from what remained of the datacentre wing and salvage all the data.
If you care about your data, you want a backup that is off-site. Cloud backup is quite inexpensive these days.
I also thought that way in the beginning, but then disaster recovery is too inconvenient and will take weeks to set everything to your standards, while with raid you just replace the drive and go
Not to mention that “temporary” directory that was supposed to last one week and wasn’t included in the backup script, but then happened to last several months holding important files
Depends on how attached you are on your data, if you have a backup, if you can do without the data created between backup cycles and how long you can wait for the restore to finish.
Everything will fail. For me, everything on single disk is expendable or backupped and can be done without when I loose a day/week of data. Everything else is on raid 1 (hdd) and in a backup schedule (external hdd).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Raid5 (well raidz1) has saved my ass multiple times. Just down forget to also raid your efi and swap partitions
It depends how valuable your data is, what backup strategy you have, and how long you’re prepared to wait to get access to your data when a drive fails.
Personally if/when I migrate my main dataset to SSD, I’ll stick with RAIDZ2/RAID6.
SSD’s are cheap nowadays. They’re also much more reliable than HDD’s. That said, when they fail it’s usually catastrophic failure with total data loss.
If your data that’s important to you, I would still use redundant storage. Especially since the cost is minimal.
The cheaper SSDs can be very failure-prone though. I actually use second-hand spinning disks in my server and I have a whole bunch of spares waiting in the wings. I am still backed up though.
As someone else has pointed out, it really depends on your use case. Although I personally keep my drives (SSD & HDD) in a redundant RAID configuration as my data is largely mission-critical.
I’ve had SSDs go bad. So if it’s something you really care about I’d approach it the same as hard disks.
At least with spinners you often get enough advanced warning of impending doom via SMART. Critical stuff I am still keeping on spinning disks backed up to tape and a privacy-respecting cloud service.
Ask you a single question: will you break a sweat of you lose your data?
If the answer is anything but a clear, immediate “NO”, go with raid even on SSDs.
(just to add, and clarify - no more than 2 disks)
Like others said: it depends.
In my opinion the most important thing to have is an off-site backup. If you have achvieved that, it’s only a matter of how long you are willing to wait for the recovery. If your answer is something like “it cannot wait” then you should go with at least raid 1 and consider additional meausres for the event when your whole array fails.
Maybe as a side note: a mirror raid does not only provide data redundancy but also improves read speeds. For SATA limited SSDs this can be interesting.
SATA SSDs don’t really make sense nowadays anymore. Last time I checked, they cost the same and are actually the exact same thing, except SATA SSDs have a big, mostly empty, plastic case around them and use a slow connector
How, with a couple of hba I can connect connect easily dozens of sata SSDs to a consumer motherboard, while doing the same with nvme drives not exactly as easy or cheap
Sure, except that it is hard to connect several NVMe SSDs to an older mainboard.
I’m quite disappointed by most comments so far talking about RAID and data loss. That is not what RAID is for at all.
RAID is for uptime/availability. When a drive fails, the system will keep running and working. For companies, that would lose thousands of currency per hour with a downtime, this is super important that the system keeps running. At home, it’s convenience that you can order a new drive and replace without hours of setting up and copying before you can watch the next episode again.
Backups are against data loss. If a single drive fails, a RAID fails or you get some encryption malware or an employee destroys stuff on purpose, then everything is destroyed. It doesn’t matter if it was a single, any RAID, HDD or SSD. You order a new drive, make a new volume and restore the data from your backup.
Well, more specifically it is protecting against a specific form of data loss, which is hardware failure. A good practice if you’re able is to have RAID and an offsite/cloud backup solution.
But if you don’t, don’t feel terrible. When the OVH datacentre had a fire, I lost my server there. But so did a lot of businesses. You’d be amazed at how many had no backup and were demanding that OVH somehow pry their smouldering drives from what remained of the datacentre wing and salvage all the data.
If you care about your data, you want a backup that is off-site. Cloud backup is quite inexpensive these days.
I also thought that way in the beginning, but then disaster recovery is too inconvenient and will take weeks to set everything to your standards, while with raid you just replace the drive and go
Not to mention that “temporary” directory that was supposed to last one week and wasn’t included in the backup script, but then happened to last several months holding important files
Depends on how attached you are on your data, if you have a backup, if you can do without the data created between backup cycles and how long you can wait for the restore to finish.
Everything will fail. For me, everything on single disk is expendable or backupped and can be done without when I loose a day/week of data. Everything else is on raid 1 (hdd) and in a backup schedule (external hdd).
I think it depends on the usage actually. Will there be lots of read and writes? SSDs are quite reliable nowadays.