@vermaden
It may look like I was joking but making such a backup is technically simple.
300TiB / 24TiB per HDD is 12.5 drives
300TiB / 16TiB is 18.75 drives
In reality it's more complex.
A 16TiB HDD is not 16TiB but 16TB lineair
Given a typical 4TB HDD I get just 3.64TiB in partitoned EXT4 HDD Space
That is 91% of the 4TB HDD
At 16TB that is 14.56 TiB {yes the loss is enormous and those hard drive companies are idiots because computer systems count in base² Binary not base10}
A 16TB drive is actually a 14.56 TiB Drive, it should be sold as 14.56 TiB not 16TB because that is misleading and false advertisement.
With these parameters we will need in reality 300 TiB / 14.56 TiB = 20.6
So we will need 21 drives for the task at 14.56 TiB. In the replication you will need twice the amount
This would become a JBOD just a bundle of drives, which is the easiest form to concatenate hard drive space to together.
A 4U JBOD enclosure can harbour a lot of drives. At the most you will need two.
Double the amount if you want a local backup of your main Spotify data.
Then you will need a 1U case for the computing System. A typical server motherboard, 1x AMD EPYC CPU, 512GB ram is more than sufficient.
You will need Fast Access to the Drive Array. 10GBit / sec in duplo should be enough. That means that your switches cables and network infrastructure will be expensive.
The high cost of AC power globally, can be a limiting factor when you have to power 42 hard drives provided that you are a Soho Network Builder, though.
That is the only factor you cannot calculate with constants
^Z
#HDD #EXT4 #partitions #Linux #technology #InfoSec #passwords #Spotify #breach #300TB
PLA_906114