WEBVTT

00:00:00.000 --> 00:00:06.640
when dream needed a server that could store unlimited gameplay footage with a

00:00:04.560 --> 00:00:11.120
matching budget he knew there was only one place to go yo

00:00:09.440 --> 00:00:15.120
and we're going to be building it in true dream fashion that's right we're

00:00:13.120 --> 00:00:24.160
going to be speed running the creation of a 1.2 petabyte hard drive storage

00:00:18.560 --> 00:00:26.480
server with a 200 terabyte all NVMe SSD

00:00:24.160 --> 00:00:29.480
server all we need is a little bit of help

00:00:31.359 --> 00:00:37.600
all right i think we're going for a world record here guys kyogsi has

00:00:35.440 --> 00:00:41.840
sponsored the SSD so that's taken care of 45 drives practically built the

00:00:39.680 --> 00:00:46.960
server for us and you guys are all here to witness it starting with the big face

00:00:44.239 --> 00:00:52.760
reveal you ready okay it's more of a faceplate but look

00:00:48.559 --> 00:00:52.760
it's a really cool one it has dream on

00:00:59.840 --> 00:01:06.240
let's go jakey oh jesus oh server to build your voice oh this is a lot of

00:01:04.080 --> 00:01:10.080
drives to shuck because the servers for dream some of the hardware did end up

00:01:07.920 --> 00:01:15.200
getting sent to us but the hard drives were not one of those things meaning

00:01:12.080 --> 00:01:16.880
that yes my friends dream actually did

00:01:15.200 --> 00:01:20.200
shell out for 60 the full

00:01:19.119 --> 00:01:26.320
60 20 terabyte hard drives that's going to

00:01:23.280 --> 00:01:28.000
be a total of 1.2 petabytes of raw

00:01:26.320 --> 00:01:31.920
storage which should work out to somewhere in the neighborhood of one

00:01:29.840 --> 00:01:34.479
petabyte of usable storage when we're done here i think we're going to play

00:01:33.119 --> 00:01:39.840
this one a little bit safer i'll put some hot spare so it might be more like 900 okay sure that's fair enough i don't

00:01:38.320 --> 00:01:44.079
want to get a tech support call realistically from like wherever the

00:01:41.759 --> 00:01:48.399
crap dream is from the server hardware itself was provided by 45 drives and

00:01:46.159 --> 00:01:54.720
this is their turbo tier server it's got a 26 core xeon gold 512 gigs of ddr4

00:01:52.960 --> 00:01:59.920
memory which we'll be using as a zfs read cache we've got four lsi hbas which

00:01:58.000 --> 00:02:04.560
are allowing us to hook up all of these freaking drives and

00:02:02.320 --> 00:02:10.640
we actually got them to send a dual port

00:02:06.520 --> 00:02:13.200
25 gigabit per second network card which

00:02:10.640 --> 00:02:17.599
um sorry 45 drives we're actually going to steal from this server and put in the

00:02:15.280 --> 00:02:21.280
SSD server and there is a reason for this

00:02:19.040 --> 00:02:25.680
the fancy switch hey i need more drives Jake hold on shut up world record the

00:02:23.440 --> 00:02:28.879
fancy switch that ubiquity sent happens to have

00:02:26.800 --> 00:02:32.319
two 25 gig ports so i'm thinking we put them together aggregate 50 gig to the

00:02:31.120 --> 00:02:37.519
storage server wow it's probably excessive but we're gonna do it anyways honestly though

00:02:35.519 --> 00:02:42.160
outside of our own server room he is getting the

00:02:39.120 --> 00:02:44.080
finest storage setup out of probably

00:02:42.160 --> 00:02:48.000
anyone else on youtube or twitch by the way Jake can i just shout you out for

00:02:46.239 --> 00:02:51.680
putting these in exactly the correct orientation for me to just am i slot

00:02:50.319 --> 00:02:55.280
them right in are you being sarcastic are you not trying to no no i was

00:02:53.360 --> 00:02:57.840
actually no it's like the most ergonomic thing ever i just grabbed them and put

00:02:56.640 --> 00:03:04.000
them in okay i'll be sure to do it the other way now oh you piece of crap

00:03:01.120 --> 00:03:08.080
why did i say anything i was not trying at all it just happened to be how they

00:03:05.760 --> 00:03:11.840
were getting pulled out that's it are we done

00:03:09.159 --> 00:03:16.319
1.2 petabytes you know it's not that fun when it's

00:03:13.120 --> 00:03:17.440
this easy what i mean it's i'm now i'm

00:03:16.319 --> 00:03:22.000
still into it we haven't found out if it works yet so

00:03:19.360 --> 00:03:27.120
we're replacing this dual 25 gigabit nick with this dual 10 gigabit nick and

00:03:24.879 --> 00:03:31.680
the reason we're doing that is that i mean they're hard drives realistically

00:03:29.360 --> 00:03:36.799
if we manage to get you know what 20 gigabit trunks so two gigabytes a second

00:03:34.400 --> 00:03:40.400
out of it that'll be fine i mean it'll just it'll do a lot more than that but

00:03:38.640 --> 00:03:45.040
you're just using this for archives so yes well yes and no i think it's possible

00:03:43.280 --> 00:03:47.920
that they could end up editing partially off of it if they were working on a

00:03:46.319 --> 00:03:51.920
project it'll have plenty for that called back from you know a previous

00:03:49.599 --> 00:03:55.599
video or something along those lines come on

00:03:53.200 --> 00:04:00.239
Jake what what was the ergonomic rationale behind

00:03:58.080 --> 00:04:03.200
putting this server here i'm not saying you're wrong i'm just saying i don't see

00:04:01.680 --> 00:04:06.400
how you're right are you complaining because you're short no

00:04:06.480 --> 00:04:12.840
i'm complaining because tall people don't consider my short person needs

00:04:11.120 --> 00:04:17.440
that's what i'm complaining about right right very important distinction

00:04:15.519 --> 00:04:21.359
unlike the petabyte of hard drive based storage this one actually

00:04:21.600 --> 00:04:30.080
is going to have a ton of room for expansion and that is thanks to

00:04:26.560 --> 00:04:32.400
high density drives like the cm6 from

00:04:30.080 --> 00:04:38.560
kyogre these puppies are available in up to what 15.3 terabytes of top this is a

00:04:35.680 --> 00:04:46.560
30 terabyte what shut up it's not not only is it a 30 terabyte SSD it's a 30

00:04:40.960 --> 00:04:46.560
terabyte tlc SSD it's not even qlc

00:04:46.800 --> 00:04:53.360
these are crazy kiosks just sent these for dream where's mine well they sent 15

00:04:52.000 --> 00:04:58.080
for dream and i was like yeah we'll just give them like seven oh really yeah it's

00:04:56.240 --> 00:05:02.080
not like he paid for them yeah that still means he's gonna end up with 120

00:05:00.000 --> 00:05:06.400
terabytes of usable space with two parity drives and a hot spare

00:05:06.639 --> 00:05:13.840
wrap your brain around it right this is the state of the art i mean i

00:05:11.039 --> 00:05:17.919
think they're looking at what 22 to 26 in the next year and those aren't even

00:05:15.440 --> 00:05:23.440
conventional those are shingles exactly this has 50 more capacity than this

00:05:21.120 --> 00:05:27.039
in a fraction of the size mind you it's probably

00:05:24.639 --> 00:05:31.680
quite literally 20 times the cost not to mention this is PCIe gen 4

00:05:29.759 --> 00:05:35.280
these will do almost 7 gigabytes a second read on a single drive

00:05:36.160 --> 00:05:43.440
and that's why we're keeping some yes you should okay so we're gonna do a four

00:05:39.199 --> 00:05:47.039
node actually wait the what oh my oh my

00:05:43.440 --> 00:05:47.919
god oh my god how do you do that you

00:05:47.039 --> 00:05:55.120
just literally holy

00:05:51.280 --> 00:05:57.039
oh my god oh my god oh my god did i put

00:05:55.120 --> 00:05:59.440
it back are you kidding me

00:05:58.400 --> 00:06:05.360
dude what's the actual is wrong with you

00:06:03.520 --> 00:06:11.120
oh my god oh oh i want to throw up i really

00:06:09.280 --> 00:06:16.240
oh do you think it still works no

00:06:14.880 --> 00:06:21.280
did you hear the noise in me well it's a pretty

00:06:19.199 --> 00:06:24.639
it's a pretty bouncy floor okay the video's done i'm leaving

00:06:22.720 --> 00:06:31.870
goodbye it might still work

00:06:27.520 --> 00:06:34.000
okay lunch says it still works

00:06:34.000 --> 00:06:40.960
you know it might actually still work here's the thing i've actually talked to

00:06:38.880 --> 00:06:44.240
seagate engineers about the kind of drop testing that they do on these things

00:06:42.319 --> 00:06:48.240
there's a solid chance that thing still works

00:06:45.440 --> 00:06:53.120
what happened what nothing you talking no no i was just saying that uh you're a

00:06:50.720 --> 00:06:56.560
fine young man and i'm really proud of the way you've turned out

00:06:55.199 --> 00:07:02.000
i'm not proud of the way you've turned out this is pretty gorgeous this is the new

00:07:00.080 --> 00:07:08.880
version of the one we have right yeah that's specifically designed for epic

00:07:05.199 --> 00:07:12.800
milan so that's a 32 core 75 43p so

00:07:08.880 --> 00:07:15.199
single single processor it boosts to 3.8

00:07:12.800 --> 00:07:20.960
gigahertz i think so not quite as good as the 75 f3 yeah but that's pretty

00:07:18.720 --> 00:07:24.000
freaking incredible this thing is gonna rip are you putting the RAM in are you

00:07:22.639 --> 00:07:32.000
gonna talk about the RAM at all i'm just gonna put it in really we're speed running okay well it's gonna be 512 gigs

00:07:29.120 --> 00:07:35.360
of RAM nope what 128 128 that's it they're eight gig dimms these are from

00:07:33.680 --> 00:07:42.160
the one million dollar pc that we didn't use right microns sent us literally like

00:07:39.120 --> 00:07:45.199
flats 96. flats

00:07:42.160 --> 00:07:47.199
of these eight gig ecc 3200 modules

00:07:45.199 --> 00:07:51.280
they're fast yep they're exactly what you want just not the capacity that you

00:07:49.199 --> 00:07:54.400
want but for this for you it's perfect because we're not using RAM caching

00:07:52.639 --> 00:07:59.840
since they're NVMe drives you don't need that for zfs but he's gonna get 128 gigs

00:07:56.879 --> 00:08:04.000
anyway so we just want a nice fast CPU which for epic high speed memory is

00:08:02.560 --> 00:08:08.080
really important and then we're basically not going to

00:08:06.160 --> 00:08:13.840
hit this at all yeah i mean stuff will go through it but that's it that's

00:08:10.080 --> 00:08:16.879
pretty much it 46 47 48 49 50 51 52 53

00:08:13.840 --> 00:08:18.720
54 55 36 57 58 59

00:08:16.879 --> 00:08:22.240
that's it shut up it does not there's only 59 yeah because it starts at zero

00:08:20.879 --> 00:08:26.479
oh hold on there might be 60 actually hold on it starts at zero doesn't it it

00:08:24.080 --> 00:08:30.240
might start at zero might be okay that it does are you screen recording there's

00:08:28.000 --> 00:08:33.919
the moment yeah i'm not screen recording but it does start at zero there is 60.

00:08:32.479 --> 00:08:39.440
that doesn't necessarily mean one of them isn't completely buggered okay

00:08:36.800 --> 00:08:43.519
cooler time yeah wow this is a beefy cooler for a two years yeah the

00:08:41.360 --> 00:08:47.200
nice thing about a 2u is you get double the cooler capacity which means

00:08:45.200 --> 00:08:49.440
your fans get to spin a lot slower yeah which is going to be good for at your

00:08:48.640 --> 00:08:54.000
house yeah one user like we're using a similar

00:08:52.000 --> 00:08:57.680
machine to this at my place right yeah okay just a less cool one oh really so

00:08:56.240 --> 00:09:01.920
dream's going to have a better server than me yeah i'm feeling pretty

00:08:59.519 --> 00:09:07.920
inadequate right now i love these tool-less sleds man when i built the

00:09:04.240 --> 00:09:09.519
first NVMe wanik it took frickin forever

00:09:07.920 --> 00:09:13.600
and i didn't even put all the screws in oh these are so much easier to deal i

00:09:12.160 --> 00:09:19.200
can't believe that every one of these is 30 freaking

00:09:16.320 --> 00:09:23.680
terabytes i just installed 60 terabytes of SSD storage hold on here comes number

00:09:22.480 --> 00:09:29.760
90 90. like freaking what i mean we do have

00:09:27.040 --> 00:09:33.279
more we can put more they're dense yeah they're i was going to grab one of the

00:09:31.279 --> 00:09:38.560
cd6s which are like the not enterprise ones um they are substantially heavier

00:09:36.080 --> 00:09:41.680
these things are dense as here david catch

00:09:39.519 --> 00:09:47.360
i don't know i know hold on a second no i want to i want to open it what no yeah

00:09:44.399 --> 00:09:52.320
no yeah chill jesus just relax what's the worst that can happen i lose the

00:09:48.800 --> 00:09:52.320
screws and we can't put it back together

00:09:54.160 --> 00:10:01.040
it's got a multi pcb design oh my god

00:09:58.399 --> 00:10:05.040
of course it does oh my god these caps though that's gonna be the difference

00:10:02.959 --> 00:10:08.959
these are their actual enterprise capacity they're willing to say it's

00:10:07.440 --> 00:10:14.480
enterprise this is for power loss protection these

00:10:11.120 --> 00:10:16.640
capacitors ensure that if any data is

00:10:14.480 --> 00:10:21.760
sitting in a cache or in a dram cache for example it can be flushed to nand

00:10:19.440 --> 00:10:26.000
before the drive actually powers down even in the event of a sudden power loss

00:10:23.600 --> 00:10:30.160
to the server that's freaking cool and those are

00:10:27.200 --> 00:10:34.800
huge look at the little holes wait they have cooling for the caps

00:10:33.200 --> 00:10:39.680
that's amazing wow i'm so happy right now that's so

00:10:37.519 --> 00:10:43.760
much nan how much nand is that man hold on we gotta find more nand we're going

00:10:41.600 --> 00:10:49.120
on a we're going on a voyage oh there's a clip there's a clip here no hold on

00:10:45.839 --> 00:10:50.640
hold on oh my god this is so cool oh i

00:10:49.120 --> 00:10:53.760
never get a chance to play with stuff like this god damn it

00:10:54.000 --> 00:11:00.480
there's another layer hold on so they got thermal pads between

00:10:59.279 --> 00:11:07.839
oh my god Jake i think it's three layers

00:11:04.640 --> 00:11:09.440
Jake no stop please stop hold on please

00:11:07.839 --> 00:11:15.200
please relay i can't do this i think it's three

00:11:12.839 --> 00:11:19.440
legs on how do we get this layer my heart there it goes

00:11:17.160 --> 00:11:21.839
holy balls it's got

00:11:20.800 --> 00:11:27.680
four dram cash dies what about that

00:11:24.079 --> 00:11:29.040
controller that thing is huge

00:11:27.680 --> 00:11:31.839
hold on here it goes here it goes here it goes oh

00:11:31.920 --> 00:11:36.880
ain't wait there's more

00:11:35.360 --> 00:11:41.920
gas well that's the thing is the higher

00:11:38.800 --> 00:11:44.399
capacity you go for your nan flash the

00:11:41.920 --> 00:11:49.600
more dram cash you need and if you're gonna have 30 freaking terabytes demand

00:11:47.519 --> 00:11:53.680
you're going to need a lot of dram eight gigabit one g by eight

00:11:52.079 --> 00:12:00.880
so it's one gig so it'd be eight gigs i guess eight gigs of flippin RAM

00:11:56.959 --> 00:12:03.040
this SSD has as much as most people's

00:12:00.880 --> 00:12:06.079
gaming machines there's a new update i brought out the unify switch we were

00:12:04.480 --> 00:12:10.399
kind of originally thinking we might build a whole rack and send it to him

00:12:07.920 --> 00:12:13.920
but then apparently his like installers are doing a bunch of crap so we're just

00:12:12.079 --> 00:12:18.240
gonna give him the switch yeah this switch has two 25 gig ports that we're

00:12:16.000 --> 00:12:21.440
going to aggregate together to be 50 gig for NVMe server totally probably

00:12:20.079 --> 00:12:25.680
overkill for what he's doing and then we're going to do two 10 gigs aggregated

00:12:23.279 --> 00:12:30.160
together for 20 gig to the hard drives then all these other ports are 10 gig to

00:12:28.399 --> 00:12:35.200
the rest of the house so that means if for whatever reason they expanded and

00:12:32.880 --> 00:12:40.000
had like a whole team of editors there they could have five people concurrently

00:12:37.760 --> 00:12:44.560
hitting this boy for 50 gigabits a second and this boy for 20 gigabits a

00:12:42.240 --> 00:12:47.839
second that is a lot of throughput for game play and if you really wanted you

00:12:46.000 --> 00:12:50.959
could switch this to a 4x10 card and then you could have 40 gig each editor

00:12:49.360 --> 00:12:54.639
will get its own 10 gigabits it's pretty sick it's a nice little switch ah you

00:12:53.440 --> 00:13:00.480
were gonna show me something cool there's a new view yeah hey look so they added this new port view so now instead

00:12:58.480 --> 00:13:05.760
of having to edit a port one by one you can go hey i wanna edit that one that one that

00:13:03.760 --> 00:13:11.519
one that one and maybe this one over here oh that's cool and you can set

00:13:08.639 --> 00:13:16.240
bam i only want this now security-minded folks might put Mac Address like limits

00:13:14.160 --> 00:13:19.839
so only that one Mac Address can connect to that port it's a nice security thing

00:13:18.240 --> 00:13:23.440
you can also see what device is connected to a specific port a lot

00:13:21.279 --> 00:13:26.639
easier so i can just click on it so i plug the bmc into that one port and then

00:13:25.760 --> 00:13:32.800
i just click on that there's the ip here's a cool feature for ubiquity it would be

00:13:30.320 --> 00:13:36.000
really nice to be able to take this go yes that's the device that i want and

00:13:35.040 --> 00:13:39.680
just set a rule that only that Mac Address

00:13:38.079 --> 00:13:43.920
can connect to that port just with one click here yeah if you just go like a

00:13:41.279 --> 00:13:46.639
limit yeah lock Mac Address lock that would be cool i bet they'll do it

00:13:45.600 --> 00:13:51.839
they're probably gonna watch this and they're probably going to do it yeah they might do it hey guess what it works

00:13:50.000 --> 00:13:56.800
now i got a vga cable because i thought the ipmi was broken turns out they

00:13:54.320 --> 00:14:00.720
screwed up i love you Gigabyte but they sent a server that doesn't support milan

00:13:59.440 --> 00:14:05.279
chips no it's a roam server it's a roam server do

00:14:03.199 --> 00:14:10.720
we have any roam chips to we do so we had a 75 or 70 402 p which is a 24 core

00:14:08.720 --> 00:14:15.360
still going to be plenty for this yeah for the

00:14:13.120 --> 00:14:19.120
cut down drive configuration that we put in here anyway yeah

00:14:17.440 --> 00:14:22.639
okay it's gonna be great okay so now it'll actually be great yeah

00:14:21.120 --> 00:14:26.800
we're in truenast now on both of them we're gonna be using trinas core as much

00:14:24.399 --> 00:14:30.480
as i like scale core is a little more production ready yeah and we want this

00:14:29.199 --> 00:14:34.639
to just work and him not to have to screw with it and this is actually

00:14:32.560 --> 00:14:40.000
shockingly user friendly to use these days back in the early frenzy oh boy you

00:14:37.519 --> 00:14:45.120
had to kind of be nerdy enough that you could have basically done it yourself in

00:14:41.600 --> 00:14:46.800
Linux anyway now man this gui is so

00:14:45.120 --> 00:14:49.839
pretty okay linem ti which one do you want to start

00:14:48.240 --> 00:14:54.800
with i want to start with the one that definitely has a working drive in this

00:14:52.800 --> 00:14:58.930
slot right here i will admit there are 60 functioning

00:14:57.199 --> 00:15:00.639
drives in the server presently

00:15:00.639 --> 00:15:05.760
i will not admit that i don't think or

00:15:03.920 --> 00:15:09.120
that didn't make sense i will not admit that i don't think

00:15:07.120 --> 00:15:11.519
i think that drive will die faster than the other ones

00:15:10.320 --> 00:15:17.760
that's nice but that wasn't the bet

00:15:13.839 --> 00:15:17.760
i'll buy you lunch whatever yes

00:15:17.920 --> 00:15:23.839
why would you do that it's fine it's fine don't touch it yet it's still

00:15:22.320 --> 00:15:26.880
spinning i'm letting it still spinning it's letting it spin wiggle wobbling

00:15:25.839 --> 00:15:31.199
barely i can't believe you bought a petabyte i

00:15:29.760 --> 00:15:34.720
can't believe you threw that hard drive can we just cut back to that for a second

00:15:38.560 --> 00:15:45.120
holy crap i can't believe you did that okay

00:15:42.560 --> 00:15:50.320
so we want some pretty chunk-tastic raid zenis i'm figuring maybe not

00:15:48.079 --> 00:15:55.360
15-drive v-dabs like we do i was thinking to do 10-drive z2s or i mean

00:15:53.920 --> 00:16:00.720
for like performance apparently the optimal is six drives but that's a lot

00:15:57.759 --> 00:16:04.800
of capacity loss yeah we'd have to do z1s at that point and i really don't

00:16:02.480 --> 00:16:09.440
want to do that so raid z2 is kind of like raid 6 where you can

00:16:07.600 --> 00:16:15.199
lose two of your drives before you actually lose any data but it means that

00:16:12.240 --> 00:16:20.959
two drives out of whatever the v dev size you have are lost in terms of

00:16:17.519 --> 00:16:22.959
capacity so raid z1

00:16:20.959 --> 00:16:27.360
sets aside only one of those drives for parity data but that means you can only

00:16:24.880 --> 00:16:32.800
sustain one loss before your next loss is going to cost you data so for dream

00:16:30.560 --> 00:16:38.000
you're thinking 10 well hold on i just realized we want to have some hot spares

00:16:36.399 --> 00:16:42.480
we don't want ten why don't we do this why don't we do four hot spares one for

00:16:40.240 --> 00:16:46.560
each bank and then and then we can do seven drive v dams

00:16:44.800 --> 00:16:51.040
upgrade z2 we're gonna lose a lot of capacity

00:16:47.920 --> 00:16:52.639
why don't we go 14 drive v devs then

00:16:51.040 --> 00:16:56.320
raid z3 so that would allow three drives lost

00:16:55.440 --> 00:17:02.480
per one of these rows sure with a spare okay so if we do raid

00:17:00.079 --> 00:17:05.839
z3s 14 drives we get 800 terabytes usable i'm about to blow your mind how

00:17:04.240 --> 00:17:10.559
much is each of these drives worth uh like 600 six six hundred that's like six

00:17:08.000 --> 00:17:14.480
hundred bucks six hundred dollars okay let's do some quick math real quick here

00:17:12.400 --> 00:17:20.559
okay six hundred twelve hundred twenty four hundred okay

00:17:16.559 --> 00:17:23.520
five thousand ten thousand ten thousand

00:17:20.559 --> 00:17:29.360
dollars worth of drives is sitting doing nothing there will be no data actually

00:17:26.400 --> 00:17:35.200
stored on them okay they're just holding data just in case these ones fail

00:17:32.480 --> 00:17:39.919
or standing there ready to go in case these fail 10 grand that level of

00:17:37.600 --> 00:17:43.679
redundancy costs in a server like this look at all this

00:17:41.120 --> 00:17:48.640
big data big data you're going to set it to be an smb share

00:17:46.880 --> 00:17:52.080
we're gonna go into advance i'm gonna do z standard compression because it's

00:17:50.640 --> 00:17:57.280
really great record size of one mag because it's all

00:17:54.160 --> 00:18:00.320
footage bam now we can store stuff big

00:17:57.280 --> 00:18:02.400
data so it works out to be 740 tera tibi

00:18:00.320 --> 00:18:05.919
bytes usable after formatting that's a big data all right let's do the NVMe

00:18:04.960 --> 00:18:11.440
we're going to do it pretty similar to the petabyte server where we have a hot spare but we're just doing one and it's

00:18:09.280 --> 00:18:16.160
a raid z2 which means we have two disks of parity that is so overkill it is with

00:18:14.160 --> 00:18:20.400
a hot spirit do you want to get a phone call hold on the problem with ssds hear

00:18:18.480 --> 00:18:23.440
me out the problem with ssds they're not like hard drives where they kind of

00:18:21.600 --> 00:18:27.120
staggered fail usually when you have like 20 ssds and they're all from the

00:18:25.440 --> 00:18:34.720
same batch they'll just start failing at the same time because they're so much more dependent on like right endurance

00:18:31.440 --> 00:18:36.720
it's better to be safer he's got 100 tv

00:18:34.720 --> 00:18:41.440
bites that's so much that's that's more than we have i know but this is like

00:18:40.160 --> 00:18:48.880
90 terabytes of SSD storage just

00:18:46.160 --> 00:18:53.120
not being used well it's being used Jake i think it's fine raid z1 and a hot

00:18:51.679 --> 00:18:58.480
spare i know their enterprise drives he's barely

00:18:56.960 --> 00:19:02.240
going to touch these compared to the workloads they're designed for you're

00:19:00.480 --> 00:19:05.600
you know i'm looking around i see wendell like through the camera

00:19:06.799 --> 00:19:13.360
hey there mr wilson it's me Linus the menace

00:19:11.440 --> 00:19:18.400
well Jake and i are having a bit of a debate right now we've got seven of

00:19:15.520 --> 00:19:23.200
these 30 terabyte keyoxia drives and i'm not going to tell you who is in which

00:19:20.559 --> 00:19:29.039
position so that you're unbiased but there are two potential configurations

00:19:26.160 --> 00:19:33.360
for them in in true nas here um are you willing to weigh in on on which one you

00:19:31.120 --> 00:19:38.960
think is proper one of us wants to do

00:19:35.360 --> 00:19:42.160
a raid z2 with a hot spare and one of us

00:19:38.960 --> 00:19:43.760
wants to do a raid z1 with a hot spare i

00:19:42.160 --> 00:19:48.559
would probably do everything honestly

00:19:46.480 --> 00:19:54.400
a little bit more it's a little bit more dangerous

00:19:51.360 --> 00:19:56.559
um but those drives are so fast

00:19:54.400 --> 00:20:00.400
and if you're on top of it it's probably okay but what if they're

00:19:58.000 --> 00:20:03.760
not on top of it if you're not on top of it then you gotta go

00:20:01.919 --> 00:20:06.720
do you really think it's likely that we're gonna hit these drives hard enough

00:20:05.280 --> 00:20:11.600
that we should be concerned about their lifespan if you get a hot spare on the

00:20:08.799 --> 00:20:14.240
flash side i would probably just make it raise d2 instead of having a hot

00:20:13.360 --> 00:20:21.039
spare only because flash wears differently than mechanical hard drives now okay so

00:20:18.640 --> 00:20:25.360
what about a raid z2 and a hot spare oh my god Jake okay all right let's just go

00:20:23.280 --> 00:20:28.480
raid z2 then with seven drives we need to put some footage on this thing nice

00:20:26.880 --> 00:20:32.240
it's going through my workstation so it's not going to be that fast wow even

00:20:30.400 --> 00:20:37.520
through your workstation it's doing 400 plus megabytes a second

00:20:34.480 --> 00:20:39.039
you know what i should go jump onto mine

00:20:37.520 --> 00:20:43.120
and hit it at the same time and see if that even goes down i bet it won't

00:20:41.200 --> 00:20:48.320
the bottleneck is going to be your your station not this machine okay well

00:20:46.640 --> 00:20:53.120
i'm still copying at 400 to 450 megabytes a second how about

00:20:50.720 --> 00:20:58.159
you okay you ready for me to press go oh you haven't pressed go yet okay i

00:20:54.880 --> 00:20:58.159
already did yeah that's what i figured

00:20:59.360 --> 00:21:05.440
yeah the one thing to consider is because we're copying like a folder full

00:21:03.280 --> 00:21:08.720
of a bunch of little files Windows will never really get there because it's like

00:21:07.200 --> 00:21:13.600
starting stopping starting zapping starting stopping but that's still super

00:21:11.440 --> 00:21:18.000
awesome this is really important just because we have

00:21:14.840 --> 00:21:20.080
redundancy okay so we have that extra

00:21:18.000 --> 00:21:24.480
couple of drives that can fail doesn't mean that we have backup

00:21:22.960 --> 00:21:29.120
so if this is where they're going to store their active projects then if

00:21:26.640 --> 00:21:33.760
something were to go wrong let's say uh a power supply blue i mean

00:21:31.440 --> 00:21:37.360
theoretically those are also redundant so you could just you

00:21:35.919 --> 00:21:41.520
could just yank one in the middle of operation but let's say it blew in such

00:21:39.200 --> 00:21:45.360
a catastrophic way that it lit on fire okay the server is dead but somehow the

00:21:43.360 --> 00:21:48.880
fire doesn't spread outside the steel chassis and light the other server on

00:21:46.799 --> 00:21:53.679
fire we need a backup that backup is gonna go automatically

00:21:51.360 --> 00:21:57.600
from this server to this one unfortunately eating up some of our

00:21:55.520 --> 00:22:01.679
capacity but not that much it's gonna be incremental so but each time it backs up

00:21:59.919 --> 00:22:05.200
it's it's keeping what's already on there and just adding the new stuff yes

00:22:03.440 --> 00:22:09.200
and it will cycle automatically so we can set it so it keeps like a daily

00:22:07.120 --> 00:22:12.559
backup uh for two weeks and it automatically deletes the old ones when

00:22:10.799 --> 00:22:15.360
it makes the new ones and doesn't store a bunch on here

00:22:13.919 --> 00:22:19.840
and then as soon as they delete something from here that will eventually

00:22:17.840 --> 00:22:25.440
fade out of those daily or weekly backups until the only copy that exists

00:22:23.200 --> 00:22:31.039
is the archival copy which like us dream has said is not

00:22:28.240 --> 00:22:34.480
super essential it's a nice to have not a need to have because you can always go

00:22:33.039 --> 00:22:39.280
re-download it off of youtube if it comes to that that's your off-site

00:22:36.240 --> 00:22:41.200
backup essentially thanks youtube okay i

00:22:39.280 --> 00:22:45.679
started the backup it's backing up from this server

00:22:43.120 --> 00:22:50.000
over to this server and it's running at 400 megabytes a second i mean that's a

00:22:48.159 --> 00:22:54.000
lot of data you could probably get it to go faster

00:22:51.440 --> 00:22:57.039
by disabling like secure ciphers on ssh but right now we just have it in the

00:22:55.520 --> 00:23:01.200
default configuration just to show that it works and since by default this is

00:22:58.960 --> 00:23:05.760
only going to be a daily backup it's got 24 hours to move whatever is on here

00:23:03.840 --> 00:23:09.440
that's plenty enough if you guys enjoyed this video check out kyoccia's products

00:23:07.840 --> 00:23:13.760
they've got everything from enterprise to consumer grade SSD products we're

00:23:11.679 --> 00:23:17.360
gonna have them linked down below also major shout out to Gigabyte who sent

00:23:15.760 --> 00:23:22.000
over the wrong server but they did send a server so kudos for that micron for

00:23:19.840 --> 00:23:26.799
sending over the RAM AMD for providing the CPU that we couldn't use thanks

00:23:23.520 --> 00:23:29.840
Gigabyte um and also 45 drives for

00:23:26.799 --> 00:23:32.240
sending over this epic storinator that

00:23:29.840 --> 00:23:36.000
happens to color match the green tabs on oh wow and with the dream front plate

00:23:34.640 --> 00:23:39.919
they can do like literally anything custom you want yeah it looks amazing

00:23:38.080 --> 00:23:42.480
if you guys enjoyed this video go check out uh i don't know one of the other

00:23:41.280 --> 00:23:47.039
times Jake and i worked on a server thing he'll find something petabyte of flash yeah

00:23:45.360 --> 00:23:50.640
oh yeah we need to get back going we gotta finish that but Jake is too busy

00:23:48.960 --> 00:23:54.720
helping me with my house he moved in early he's an in-demand kind of boy