WD Black in a NAS?

Associate
Joined
8 Oct 2004
Posts
2,283
Hi folks,

We're buying a Synology NAS for our small business, and we're looking for drives for it. We have a need for as fast drives as possible so the WD Blacks are currently a lot more attractive than the Reds. I know that the Reds are "designed" for NAS use but would Blacks be perfectly usable?

The drives will be written to and read from perhaps every few minutes and potentially at the same time, by 2 users, with files that could be GB large at a time, and pulling frames etc. We have tested this using a WD Black internal drive in one of the machines with both of us writing to it at the same time over a switch and it seems fine, so we're imagining it should be much the same experience when the drives are in a NAS.

Is this a reliable option or are we being stupid and should just get Reds? The speed benefit could be significant with the Blacks...

In either case we would be using RAID5. 2 drives, 1 as backup.

Cheers,
 
a) you cant have raid 5 with 2 disks, 3 is a minimum
b) Disadvantages of RAID-5 Volumes
In general, RAID-5 volumes are not well suited for any write intensive workload, since a single write is likely to generate a disk read of the parity and two writes (to update data and to parity).
c)1 as backup. - raid is not a backup
 
a) you cant have raid 5 with 2 disks, 3 is a minimum
b) Disadvantages of RAID-5 Volumes
In general, RAID-5 volumes are not well suited for any write intensive workload, since a single write is likely to generate a disk read of the parity and two writes (to update data and to parity).
c)1 as backup. - raid is not a backup

Sorry I meant RAID1. A simple mirror. RAID is a backup, of course it is. We'll also be backing up to other locations, including off-site.

Archeum - thank you. Are you sure that they're ok for simultaneous r/w operations? There's surprisingly little info out there on this.
 
WD Red Pro.

Pro are 7200RPM. Designed for NAS.

Also, RAID is not a backup. You also need to create hourly/daily/weekly backups, depending on your type of use.
I'm not trying to be awkward, more inquisitive, but can you please explain to my why redundancy protection isn't a backup?
 
I'm not trying to be awkward, more inquisitive, but can you please explain to my why redundancy protection isn't a backup?

Once you've built your RAID, you typically create one or more non-redundant filesystem(s) over it.

If you get irrecoverable corruption in that filesystem your data will be lost; no matter how many copies of the corruption you've maintained.

Similarly, if you're unfortunate/careless enough to be hit by ransomware - again, RAID won't help you get your data back.

There's plenty of other ways that you can lose data even if you've built a RAID - e.g. a few years down the line a disk fails so you replace it
and the rebuild triggers one of the other drives to fail before the rebuild completes.

Fortunately the OP has partly recognised this by acknowledging they will have other processes in place that are backups.

RAID is not a backup, it is not even part of a backup. There's two possible benefits to RAID - performance (the "I" being meant to be inexpensive,
the theory being that you could get a equivalent performance from a bunch of cheap disks vs one very expensive one) or continuity of operation
in the event of a component failure - the Redundant bit.

A Backup is an entirely separate copy of the data (ideally including filesystem metadata), typically multiple copies taken over a period of time allowing
recovery to a particular point in time if necessary. So, if you accidentally delete a file (or database table or whatever) you won't get it back if you have
a RAID, but you will if you have a backup.

I'd also second the suggestion that the OP considers the Red Pro as a (possibly more appropriate) alternative to the Black.
 
@VersionMonkey - Thanks for the feedback, and had to laugh when I realised that asking this question has resurrected a 5 year old thread. Whoops! :D

So are we saying then, that running two 10TB NAS drives in RAID 1 for instance, won't make your data recoverable if one of those disks were to fail? For argument's sake, simple folder / file systems holding media, music, photos. If that data is unrecoverable, what's the point of mirroring?

I understand your point on ransomware, although a lot of people have backup drives permanently connected to their PCs with scheduled backups, and I'd argue they'd be susceptible to the same problem. I disconnect my backup disk afterwards and store it away for this reason.

I also understand that you can't count a mirror as THE backup, which is what the 3,2,1 backup rule is about, but also can't be considered ONE of those backups?

Also understand about the incremental and version controlled backup model, but that's just one interpretation of a backup isn't it? Copying files over to a USB stick and putting them in a drawer is considered a backup, even if not as advanced as a professional backup system like Time Machine, et al.

Cheers for the help so far.
 
I also understand that you can't count a mirror as THE backup, which is what the 3,2,1 backup rule is about, but also can't be considered ONE of those backups?
RAID is Redundancy against drive failure.

It won't protect againts say failure of controller corrupting data, or anything else causing logical level data corruption.
Also badly failing PSU can fry every electric component of PC.
Lightning strike to power line could cause same.
(though data would be recoverable from physical platters by recovery company)
Neither it's protection against user error/malware, because all logical level operations are automatically done to every disk in array.

Backup needs to survive those.
 
@VersionMonkey - Thanks for the feedback, and had to laugh when I realised that asking this question has resurrected a 5 year old thread. Whoops! :D

So are we saying then, that running two 10TB NAS drives in RAID 1 for instance, won't make your data recoverable if one of those disks were to fail? For argument's sake, simple folder / file systems holding media, music, photos. If that data is unrecoverable, what's the point of mirroring?

I understand your point on ransomware, although a lot of people have backup drives permanently connected to their PCs with scheduled backups, and I'd argue they'd be susceptible to the same problem. I disconnect my backup disk afterwards and store it away for this reason.

I also understand that you can't count a mirror as THE backup, which is what the 3,2,1 backup rule is about, but also can't be considered ONE of those backups?

Also understand about the incremental and version controlled backup model, but that's just one interpretation of a backup isn't it? Copying files over to a USB stick and putting them in a drawer is considered a backup, even if not as advanced as a professional backup system like Time Machine, et al.

Cheers for the help so far.

Ah yes, I also didn't spot the thread resurrection. Whoops indeed.

But anyway. Think of it this way.

You should view a RAID as if it is a more reliable/higher performing single disk. All the things that can go wrong with a single disk other than outright failure can also go wrong with an array
and actually outright failure isn't completely eliminated either.

You format the drive and you write some files to it, but while the files are being written the power goes out and the filesystem is left in an inconsistant state. You run chkdsk, but that
says it can't fix it - your data is unrecoverable (at least without resorting to some other data recovery tool); but a mirror won't help at all because all you have is two copies of a broken
filesystem. A Windows Update causes photoviewer to overwrite the first half of every image file you open; a mirror won't help you get your photos back because all you have is two copies
of the corrupted files.

While outright failure may (in some configurations) be less likely with a RAID (that power failure could also mess with the RAID's metadata don't forget), it doesn't address all the other things
that can go wrong with storage.

RAID is there to allow you to carry on working while you order a replacement disk (while hoping that you don't get a second disk failure before the array is rebuilt - if you bought all the disks at
the same time, that's actually more likely than you might wish for).

To quote backblaze: "A 3-2-1 strategy means having at least three total copies of your data, two of which are local but on different mediums (read: devices), and at least one copy off-site". It's
the "read: devices" bit that tells you you shouldn't count a mirror as providing the two local copies: things that can go wrong with one side of the mirror will be replicated immediately to the other
side of the mirror with the sole exception of a hard failure of one of the disks. You should still have a completely independent local copy and then a 3rd (or more) off-site copy. So, yes you can count
mirror as one copy; but not because it is a mirror - you can count a single disk as one copy too. The key with that scheme is that the two local copies are independent - a mirror or other RAID doesn't
create independent copies because it is still a single filesystem.

The full, incremental and differential concepts are about balancing the storage requirements for the backup and how long they take vs how much time it would take to do a restore.

How you approach backup depends on how important the data/system is to you and how quickly you need it back when you accidentally delete your final thesis the day before it is due to
be submitted. If that's what you are trying to protect against then a copy on a USB stick in a drawer is possibly a viable backup strategy but RAID isn't.
 
Thanks for all the explanations guys, I do appreciate it.

I'm trying to apply your explanations and knowledge to my example whilst trying not to derail this ancient thread too much. I'll create another with my quandry.

Cheers!
 
Back
Top Bottom