'''R'''edundant '''A'''rray of '''I'''ndependent '''D'''isks ('''RAID''') requires two of the same drives and size. Here you're just setting up a '''J'''ust a '''B'''unch '''o'''f '''D'''rives ('''JBOD''').
+
'''R'''edundant '''A'''rray of '''I'''ndependent '''D'''isks ('''RAID''') requires two of the same drives and size. Here you're just setting up '''J'''ust a '''B'''unch '''o'''f '''D'''rives ('''JBOD''').
Mixing SSD's and HDD's in a JBOD is not like how Apple does a Fusion Drive if that was what you where hoping for. There is no means of weighing which file goes to which drive within a JBOD, this is also true with RAID as well.
As I stated you need two drives which are the same type, size and I/O to gain either striping (RAID-0) but if either drive goes you loose access to all of your data. Or mirroring which duplicates the file across both drives so you have a copy in case one of the drives goes on you (RAID-1).
Here’s some useful references:
* [https://www.cru-inc.com/data-protection-topics/raid-vs-jbod/|RAID vs JBOD]
If speed is important I would get two SSD’s and then RAID them into a RAID-0. Otherwise I would leave them as discreet drives making my boot drive the SSD with the OS & Apps, then use the HDD for my data drive. Leaving the free space on the SSD alone so the OS and Apps can leverage it for virtual RAM, paging and cache.
'''R'''edundant '''A'''rray of '''I'''ndependent '''D'''isks ('''RAID''') requires two of the same drives and size. Here you're just setting up a '''J'''ust a '''B'''unch '''o'''f '''D'''rives ('''JBOD''').
Mixing SSD's and HDD's in a JBOD is not like how Apple does a Fusion Drive if that was what you where hoping for. There is no means of weighing which file goes to which drive within a JBOD, this is also true with RAID as well.
As I stated you need two drives which are the same type, size and I/O to gain either striping (RAID-0) but if either drive goes you loose access to all of your data. Or mirroring which duplicates the file across both drives so you have a copy in case one of the drives goes on you (RAID-1).
Here’s some useful references:
* [https://www.cru-inc.com/data-protection-topics/raid-vs-jbod/|RAID vs JBOD]
If speed is important I would get two SSD’s and then RAID them into a RAID-0. Otherwise I would leave them as discreet drives making my boot drive the SSD with the OS & Apps, then use the HDD for my data drive. Leaving the free space on the SSD alone so the OS and Apps can leverage it for virtual RAM, paging and cache.
'''R'''edundant '''A'''rray of '''I'''ndependent '''D'''isks ('''RAID''') requires two of the same drives and size. Here you're just setting up a '''J'''ust a '''B'''unch '''o'''f '''D'''rives ('''JBOD''').
Mixing SSD's and HDD's in a JBOD is not like how Apple does a Fusion Drive if that was what you where hoping for. There is no means of weighing which file goes to which drive within a JBOD, this is also true with RAID as well.
As I stated you need two drives which are the same type, size and I/O to gain either striping (RAID-0) but if either drive goes you loose access to all of your data. Or mirroring which duplicates the file across both drives so you have a copy in case one of the drives goes on you (RAID-1).
Here’s some useful references:
* [https://www.cru-inc.com/data-protection-topics/raid-vs-jbod/|RAID vs JBOD]
* [https://www.cru-inc.com/data-protection-topics/understanding-raid/|UNDERSTANDING RAID]
* [https://www.cru-inc.com/data-protection-topics/understanding-jbod/|UNDERSTANDING JBOD]