WEBVTT

00:00:01.520 --> 00:00:06.319
oh my god this thing is what happened

00:00:04.960 --> 00:00:13.280
gusting oh looks like it was in a construction zone

00:00:10.400 --> 00:00:16.800
and an apocalypse and then it got snowed on oh my god it's a good thing we

00:00:15.280 --> 00:00:23.439
haven't turned it on because there's just like metal server rack hardware just sitting

00:00:20.320 --> 00:00:23.439
on the motherboard here

00:00:24.240 --> 00:00:32.640
well i think it might short out boys why are we even using this thing well we're

00:00:29.039 --> 00:00:36.160
not right now that's for sure oh

00:00:32.640 --> 00:00:36.160
i can't even lift it all up

00:00:37.760 --> 00:00:45.120
oh i don't even want to touch this

00:00:40.800 --> 00:00:47.120
i got a mask on i'm still coughing

00:00:45.120 --> 00:00:52.640
you gotta be wondering why we would use a server like this when we have a shiny

00:00:50.480 --> 00:00:58.320
new backup server like this one right over here this guy holds the backup for

00:00:55.440 --> 00:01:03.520
our main storage server wanik which has all the data for all of our ongoing

00:01:00.719 --> 00:01:07.920
projects for all of our channels so thanks to this if we somehow lost a

00:01:05.760 --> 00:01:12.560
piece or even all of that data on the main server say to drive failures or

00:01:10.080 --> 00:01:16.400
even a fire in our server room we'd have a local copy of it

00:01:14.320 --> 00:01:20.240
ready to go for our editors but what if the worst case scenario happened say

00:01:18.320 --> 00:01:27.000
there's an earthquake or a tsunami and our whole building is destroyed that is

00:01:22.960 --> 00:01:27.000
where our remote backup

00:01:27.119 --> 00:01:34.400
our remote backup over 300 kilometers away comes into play except for one

00:01:31.759 --> 00:01:38.560
small problem for the past two years it hasn't actually been working and

00:01:36.320 --> 00:01:43.280
unfortunately we've used up all of our favors from server manufacturers so

00:01:41.680 --> 00:01:47.439
we're going to try to use this thing to replace it we have no idea if it still

00:01:45.840 --> 00:01:50.479
works so good luck everybody

00:01:50.560 --> 00:01:56.479
good luck learning about our sponsor kiwi co kiwico ships out crates that

00:01:54.479 --> 00:01:59.920
contain hands-on projects for kids to help develop their creative confidence

00:01:58.079 --> 00:02:04.280
and problem-solving skills learn more at the end of the video or at the link

00:02:01.280 --> 00:02:04.280
below

00:02:10.720 --> 00:02:16.720
first order of business is let's get annie dale server out of here so that it

00:02:14.640 --> 00:02:19.920
doesn't get corrupted corrupted by the dust that's the thing you dust one

00:02:18.239 --> 00:02:25.120
server next to another server now you got two dusty servers

00:02:23.200 --> 00:02:29.280
oh my god do you want me to take that end well i'm just asking i'm just saying

00:02:27.599 --> 00:02:32.959
i'd play a lot of bad things you know i lift a lot of 80 gram weights over and

00:02:31.360 --> 00:02:37.840
over and over again this side's way nicer yeah you're good don't worry let me just sorry i just gotta scratch my

00:02:36.080 --> 00:02:40.480
back a little bit here you know we're sort of in a hurry oh

00:02:39.120 --> 00:02:44.959
yeah so let's just clean the server now then i guess oh

00:02:43.440 --> 00:02:49.519
there is wood in here yeah it might be sawdust of some sort okay we're gonna

00:02:47.519 --> 00:02:55.120
need to take this outside for the main event i agree cleaning but what is some

00:02:52.080 --> 00:02:56.239
of this stuff in here like what is that

00:02:55.120 --> 00:03:01.120
um some template for something

00:02:58.480 --> 00:03:04.400
it's like plastic too it's so dusty those of you who have been around long

00:03:02.400 --> 00:03:08.879
enough might actually recognize this as the very first storinator that we ever

00:03:06.720 --> 00:03:14.000
rolled out got that silk screen logo on the front from 45 drive so those are

00:03:10.800 --> 00:03:15.440
like ancient SATA

00:03:14.000 --> 00:03:19.760
these ones are different i put these okay this was my test server like 20

00:03:17.599 --> 00:03:23.120
years ago for like two months well you took really good care of it

00:03:21.519 --> 00:03:27.760
construction started and it's just been like actually like two years oh you know

00:03:25.440 --> 00:03:32.159
what oh that one there we go yeah

00:03:28.560 --> 00:03:34.959
a vertex ii oh my god so i've had this

00:03:32.159 --> 00:03:40.080
vertex too since i worked at ncix i don't know why we circled this at some

00:03:36.720 --> 00:03:42.799
point it's a 60 gig oh the motherboard i

00:03:40.080 --> 00:03:46.879
didn't even look in this thing properly holy

00:03:44.959 --> 00:03:52.159
yeah that's gonna be a problem

00:03:49.120 --> 00:03:53.760
like those slots like the PCIe slots and

00:03:52.159 --> 00:03:59.280
the RAM slots are those even gonna work anymore i hope so so this is a triple

00:03:57.040 --> 00:04:03.920
redundant power supply it's literally yeah it's enormous and it uses up like i

00:04:02.480 --> 00:04:08.159
don't know i don't even think we can put a different power supply in here that's another thing too is we wouldn't

00:04:06.400 --> 00:04:11.519
normally try to roll a server with such outdated hardware because of concerns

00:04:10.000 --> 00:04:16.799
about power consumption this is not efficient this is like pretty sure this is ddr3 i think it's ddr4 i don't think

00:04:15.760 --> 00:04:21.199
so 1.5 it is

00:04:19.680 --> 00:04:27.280
either way we're not that concerned about power efficiency because we don't pay for power in our rack space at that

00:04:24.320 --> 00:04:30.960
data center so hey thanks itale yeah thanks i tell

00:04:28.639 --> 00:04:34.479
hey the vertical parts aren't that bad that's how you can tell that it was uh

00:04:33.040 --> 00:04:38.320
falling dust just a little bit of drywall you know

00:04:36.479 --> 00:04:41.840
for those of you wondering what the heck went wrong here part of it is that this

00:04:40.400 --> 00:04:45.919
thing's been sitting around for a couple of years but the other part of it is

00:04:44.000 --> 00:04:49.840
that it was accidentally left in a rack that was inside a construction zone now

00:04:47.680 --> 00:04:53.759
the construction workers very thoughtfully put like they actually

00:04:51.680 --> 00:04:57.199
built a box around the rack thinking that they were protecting the delicate

00:04:55.520 --> 00:05:02.240
equipment inside i guess they didn't understand that like having a big

00:04:59.520 --> 00:05:06.639
opening in the top of it meant that the dust would go in the face

00:05:04.400 --> 00:05:11.600
anyways whatever we can fix it hopefully yeah the fact that we haven't powered it

00:05:08.720 --> 00:05:15.440
on with this dust is good though yeah if we powered it on this is almost there's

00:05:13.440 --> 00:05:20.560
almost definitely something conductive in some of this dust so this thing has

00:05:17.440 --> 00:05:22.720
64 gigs of RAM that's fine for an

00:05:20.560 --> 00:05:25.600
off-site backup i was thinking about adding more RAM but i i really don't

00:05:24.240 --> 00:05:30.400
think we need it especially if we're going to run unraid i think maybe we should vacuum it a little bit first no

00:05:28.800 --> 00:05:35.039
we can't vacuum it because there's static problems exactly

00:05:32.240 --> 00:05:39.199
we can't suck we have to blow okay okay i think this thing is going to be enough

00:05:36.560 --> 00:05:43.020
for reference here let's just uh it'll be fine

00:05:40.639 --> 00:05:49.919
all right here we go

00:05:49.919 --> 00:06:03.680
alex was like what is going on

00:06:03.680 --> 00:06:09.360
it's like new baby oh wow that's bright way more convenient than

00:06:08.000 --> 00:06:13.520
getting an air compressor yeah i mean i've i've had things like this before

00:06:11.360 --> 00:06:16.240
usually the battery-powered ones but this one

00:06:14.800 --> 00:06:20.720
complains about vacuum being too staticky sticks swiffer look we don't

00:06:19.120 --> 00:06:25.280
have to put this in the video we are putting this in the video 100 oh oh come

00:06:23.600 --> 00:06:29.840
on are you kidding me well i want it to be clean don't i oh you at least have

00:06:27.440 --> 00:06:32.960
your live strong bracelet on it's like wait wait how are you taking

00:06:31.360 --> 00:06:36.400
this off with a phillips the mounting hardware for this CPU cooler was lost

00:06:35.199 --> 00:06:40.400
and so i like ghetto found some like that are the

00:06:38.319 --> 00:06:45.360
right size and put some washers on there it works that cooler what is the acid

00:06:42.639 --> 00:06:50.479
tank zero two six four we're up to like ten thousand now oh wow this is old

00:06:48.319 --> 00:06:54.319
here's a little spring-loaded mounting screw it's just sitting here like this

00:06:54.560 --> 00:07:01.120
what is that even from this is not from this computer how is this in here thanks

00:06:59.120 --> 00:07:06.160
i hate it i just need some paper towel who keeps moving the bloody paper towel

00:07:03.199 --> 00:07:10.000
from the pc build corner i don't like kimwipes they don't have the absorbency

00:07:08.720 --> 00:07:14.880
of you want some ipa bro

00:07:11.759 --> 00:07:17.759
brandon brings the paper towel back

00:07:14.880 --> 00:07:21.280
oh well wait so you went you found paper towel but then you actually you walked

00:07:19.680 --> 00:07:24.800
in like 10 seconds after we found paper towels do you have to make noise while

00:07:22.720 --> 00:07:28.560
we're shooting i just want to there we go you know you're doing four different

00:07:26.720 --> 00:07:31.840
things you're watching tv you're playing a game you're texting on your phone

00:07:30.080 --> 00:07:35.360
you're freaking get it to land on it oh wow that was pretty good

00:07:33.759 --> 00:07:40.560
ah wait is this actually pro hold on should

00:07:37.280 --> 00:07:43.440
i should i no it's not here catch

00:07:40.560 --> 00:07:48.240
what is this thing what the sh what is this do you need some tweezers oh it's

00:07:45.919 --> 00:07:51.680
just like a little bit of wire

00:07:49.360 --> 00:07:55.599
this isn't even like a kind of wire we should be cutting in this office like

00:07:53.840 --> 00:07:59.280
it's not oh it's not network or anything Ethernet is it not no look at the color

00:07:57.599 --> 00:08:03.759
it's weird no no this is it's totally easy but also why is it in there

00:08:01.919 --> 00:08:06.319
like in the socket you should blow that off wait wait before you because this is

00:08:05.039 --> 00:08:11.039
dirty you should blow it off first here's a oh yeah that'll do

00:08:09.759 --> 00:08:17.520
clean that clean the CPU before you put it in um why do we have like

00:08:14.240 --> 00:08:19.440
200 sub to LTT wood chips what's up to

00:08:17.520 --> 00:08:24.560
LTT because they're for a sponsored pose

00:08:22.479 --> 00:08:31.120
huh how much work did you put into this like an hour oh okay

00:08:31.120 --> 00:08:36.880
can i help you at all yeah sure why don't you install some drives that'd be helpful

00:08:35.519 --> 00:08:40.399
i mean we don't even know if this thing posts that might be good to know before

00:08:38.560 --> 00:08:44.800
i even bother with this actually i'm just gonna keep installing sas cards

00:08:42.800 --> 00:08:49.600
while you do your thing okay here i am installing not one

00:08:47.440 --> 00:08:53.200
but two fast cards while you're just like slacking over there look at this

00:08:51.839 --> 00:08:56.320
i'm even gonna have all the screws in before you get the cables in i'm already

00:08:55.040 --> 00:09:02.800
done oh it's oh you got to put more than one power cable can't you tell it to shut up

00:08:59.839 --> 00:09:05.920
no you can't i can what i am god all right power supplies have a meatball oh

00:09:04.399 --> 00:09:09.440
well that's pretty good yeah can you entertain a data center if like you had

00:09:07.920 --> 00:09:12.720
a hardware failure and it just won't shut up until you fix it

00:09:11.279 --> 00:09:18.720
well i thought that was the point of a hardware failure like being noisy and

00:09:15.760 --> 00:09:22.399
all wasn't done wasn't done whatever linda i thought you said it's past the

00:09:20.640 --> 00:09:26.160
thing it's totally working all right there's could you not tell me we had

00:09:23.920 --> 00:09:29.600
that remember albion that died okay that's just give it a sec

00:09:28.000 --> 00:09:33.360
i think it's fine that was a good post yeah it's good it's good so we're using

00:09:31.279 --> 00:09:37.360
ironwool pro 12 terabytes not all of them well and then these drives are from

00:09:35.120 --> 00:09:40.720
annie are you gonna let me talk or not did you know these drives are from annie

00:09:38.640 --> 00:09:46.240
dale so with the normal raid you got the stripy stripes across the multiple

00:09:43.279 --> 00:09:50.880
drives okay with unraid it actually puts the entire file on a single drive so

00:09:49.040 --> 00:09:54.880
you're limited to single drive write speed that's the biggest problem with it

00:09:53.440 --> 00:09:59.440
for us though it's not a problem because this is going to be off-site with only a

00:09:56.640 --> 00:10:02.800
gigabit connection for our purposes this is going to be more than fine it's

00:10:01.360 --> 00:10:07.120
day two and i've got an update for you guys we actually took out the ironwolf

00:10:04.640 --> 00:10:12.320
pros because we realized another temporary server clover server was full

00:10:09.600 --> 00:10:17.519
of exos drives so now we've got 22 of them which is all we need for our

00:10:14.160 --> 00:10:19.680
off-site backup of wanik plus snapshots

00:10:17.519 --> 00:10:23.920
of older versions of it so that in case something accidentally gets deleted we

00:10:21.440 --> 00:10:29.200
can go back and get it real quick styles we also went and updated the firmware on

00:10:26.160 --> 00:10:31.200
our hbas updated the BIOS on the board

00:10:29.200 --> 00:10:35.839
updated the ipmi firmware and this thing is humming so well like i'd say it's a

00:10:33.839 --> 00:10:40.079
pretty good hummer you know because it doesn't have the greatest power

00:10:37.519 --> 00:10:44.720
consumption characteristics and it's is it like an h1 or an h2 it's a hummer

00:10:42.720 --> 00:10:48.480
oh yeah we also added a couple of 500 gig cash drives these are running in

00:10:46.240 --> 00:10:52.160
raid 1 and they're not super high performance they're just mx500 SATA

00:10:50.480 --> 00:10:56.640
drives from crucial but they're high enough performance that if we wanted to

00:10:53.680 --> 00:11:00.079
run a vm or something like that then we could and realistically they're way

00:10:58.560 --> 00:11:04.560
faster than we need since it's a one gigabit connection to this bad boy now

00:11:02.160 --> 00:11:08.079
all we gotta do is put the uh uh where'd they go

00:11:05.360 --> 00:11:13.120
where the heck the oh yes ah yes the old 45 drives mechanism for covering

00:11:11.200 --> 00:11:18.160
up the drives did they update that oh it's so much better i don't actually

00:11:14.959 --> 00:11:19.760
mind this one it's fine these rods are

00:11:18.160 --> 00:11:23.519
really stupid you're like

00:11:21.279 --> 00:11:27.440
ow damn it my finger this thing is so cute it actually looks

00:11:25.600 --> 00:11:31.360
pretty new i know it doesn't even look that old and decrepit anymore so you

00:11:29.519 --> 00:11:36.560
know where this was originally deployed no in the hallway at the langley house

00:11:34.640 --> 00:11:40.240
really yeah like you would like trip over it in the top of the stairs there

00:11:38.959 --> 00:11:45.120
now i can show you what that looks like in the un-raid software we're doing a parody sync right now so you can

00:11:43.200 --> 00:11:49.680
actually see pretty much all of our drives are reading at their maximum

00:11:47.120 --> 00:11:53.120
speed of about 200 megabytes a second the reason it's doing that is because we

00:11:51.279 --> 00:11:56.880
did change out those drives earlier today and so we need to rebuild the

00:11:54.560 --> 00:12:02.160
parity data unread does still have parity protection it's just written

00:11:59.360 --> 00:12:06.880
individually to two dedicated drives so we can lose up to two of the 22 drives

00:12:04.880 --> 00:12:10.480
that are in here without losing any data whatsoever look at that capacity i was

00:12:09.279 --> 00:12:17.519
going to say another nice thing about underage is it's got a nice easy to understand graphical interface so you

00:12:13.839 --> 00:12:20.000
can see here we've got 240 terabytes

00:12:17.519 --> 00:12:24.079
of off-site storage this is kind of fun it's an older system but

00:12:21.920 --> 00:12:28.000
kind of still checks out it's doing 3.9 gigabytes per second internally just

00:12:26.160 --> 00:12:32.079
reading all the data off those drives those poor hbas are just ripping they're

00:12:30.399 --> 00:12:37.040
they're going boys do you think if i wiggle wobble this thing around a bunch

00:12:34.240 --> 00:12:39.839
that like read speed will go down it seems like a bad idea

00:12:38.560 --> 00:12:44.800
it's all fine and good to have a bunch of storage but we're not going to be like copying things manually so what are

00:12:43.200 --> 00:12:51.040
we doing backups are only good if it does it itself right you don't want to rely on human error there especially us

00:12:48.399 --> 00:12:54.320
too unlike onex server which does a live file backup to annie dale which we built

00:12:53.120 --> 00:12:57.920
a few days ago you guys haven't really heard about that one yet um anyways

00:12:56.399 --> 00:13:01.680
sensible jellyfish fire we're calling it annie dale now it's great yeah because

00:13:00.399 --> 00:13:07.920
this thing is running unread and we don't really expect the performance to be great running a live file sync to it

00:13:05.600 --> 00:13:12.639
probably isn't the best idea even with cache drives so instead we're going to

00:13:10.240 --> 00:13:16.800
be doing snapshots and now because our backup server is running zfs we could do

00:13:14.800 --> 00:13:20.560
zfs snapshots but we actually are going to use a tool called our snapshot which

00:13:18.639 --> 00:13:24.079
is based on rsync a file transfer software that's very ubiquitous amongst

00:13:22.240 --> 00:13:28.240
the Linux community the fantastic thing about our snapshot as the name implies

00:13:26.240 --> 00:13:32.480
is it takes these snapshots but they're also deduplicated so

00:13:30.480 --> 00:13:37.920
say we have our 30 terabytes of like base footage on wanik and we add a

00:13:35.120 --> 00:13:41.600
terabyte a day yeah once it does that big backup and say we're doing hourly

00:13:39.839 --> 00:13:45.279
backups and we want to keep 24 of them so we have a whole day's worth of them

00:13:43.360 --> 00:13:49.279
rather than just like making a new copy each time it creates a new hard link

00:13:47.519 --> 00:13:52.560
which is basically like a map that's pointing to those existing files that

00:13:51.120 --> 00:13:57.920
are already there so that way when we do our new hourly backup it's only going to add the say 500 gigs from whatever

00:13:56.160 --> 00:14:01.839
ingest we just did and then it'll just point to the existing files now the

00:13:59.680 --> 00:14:05.360
question becomes what about deleted files well

00:14:03.360 --> 00:14:10.079
that's fine too because what it'll do is it'll take your new snapshot and it'll

00:14:06.880 --> 00:14:12.399
say oh hey that's not there anymore so

00:14:10.079 --> 00:14:15.839
we're just going to throw that out but we're going to leave it in your previous

00:14:13.680 --> 00:14:20.240
snapshot just in case you need it later and then what will happen is you set a

00:14:17.760 --> 00:14:25.600
policy within the software and say okay i want to keep these snapshots for let's

00:14:22.639 --> 00:14:29.199
say hourly for a week and then i want to keep that's

00:14:26.800 --> 00:14:33.519
is that i was thinking hourly for 24 hours sure and then it takes once that

00:14:31.360 --> 00:14:38.880
24 hours is up it recycles the oldest one as the daily backup so that's one of

00:14:35.680 --> 00:14:41.440
the reasons that this needs so much more

00:14:38.880 --> 00:14:44.720
storage than the wanik server that it is backing up because it's actually going

00:14:42.720 --> 00:14:49.120
to be backing up everything that was on wanik's server over the last probably

00:14:46.399 --> 00:14:52.480
month or two but when you think about it say if we do one or two videos a day

00:14:51.040 --> 00:14:57.199
realistically we're not gonna pass like a terabyte a day of new footage like i

00:14:54.720 --> 00:15:00.639
don't know david can we yeah maybe a little bit more okay whatever it doesn't

00:14:58.560 --> 00:15:05.360
matter we'll say it's a terabyte a day 30 days of that that's 30 terabytes plus

00:15:02.959 --> 00:15:09.839
the like 30 ish terabytes of like wanak we usually have should be well within

00:15:07.040 --> 00:15:13.360
the 240 we have so you give those you give those guys 100 terabytes they fill

00:15:11.600 --> 00:15:18.320
it he's been doing pretty good so far the good news is that unraid allows easy

00:15:16.240 --> 00:15:21.680
expansion of your unrate array so if we just ship a master carton of hard drives

00:15:20.240 --> 00:15:24.639
here's some more irons we can take our sophisticated rods off

00:15:23.839 --> 00:15:30.320
here and it'll be fine now to show you guys what this looks like in practice we've

00:15:28.320 --> 00:15:35.920
set up a test directory with a sort of 50 gig ish project and we've started the

00:15:33.360 --> 00:15:41.760
r snapshot hourly backup and if we look in our backup thing here we got this pdf

00:15:38.639 --> 00:15:43.920
Techquickie and look at that it's it's

00:15:41.760 --> 00:15:47.440
getting transferred yeah it's it's pretty slow because it's

00:15:45.199 --> 00:15:50.560
gigabit but it is at least going i think turbo ride is on right now so it's like

00:15:49.040 --> 00:15:55.120
got all the drives spun up but we wouldn't leave that on in practice

00:15:53.120 --> 00:15:58.959
so there it is in spite of what it looked like at the beginning of this

00:15:56.560 --> 00:16:03.600
project our off-site backup server is ready to go meaning we have a 3-2-1

00:16:01.839 --> 00:16:06.959
backup solution in place for the first time in

00:16:05.680 --> 00:16:11.360
years practicing what we preach

00:16:08.880 --> 00:16:15.120
just like i practice these segways kiwi co is our sponsor for today's video

00:16:13.759 --> 00:16:20.160
and they're a monthly subscription service to help make stem topics fun and

00:16:17.920 --> 00:16:24.000
interactive for kids of all ages they believe that if you learn small things

00:16:21.920 --> 00:16:28.880
today they can turn into world-changing ideas tomorrow so each month you'll get

00:16:26.160 --> 00:16:32.160
a themed crate to learn specific topics each crate is designed by experts and

00:16:30.560 --> 00:16:36.079
contains everything you need to complete it which means you don't need to run off

00:16:34.000 --> 00:16:39.920
to the store to get extra supplies like glue or scissors or whatever the crate

00:16:37.920 --> 00:16:43.600
that we're showing here is at a kiwi level that's for kids ages five to eight

00:16:41.680 --> 00:16:47.920
that'll teach programming and robotics another one is the eureka level for your

00:16:45.600 --> 00:16:52.079
teens ages 14 plus that highlight basic engineering and sound practices kiwico

00:16:50.880 --> 00:16:56.399
is a great way to keep your kids occupied for hours and you can check it

00:16:54.240 --> 00:17:01.279
out today at kiwico.com LTT where you'll also get 50 off your

00:16:59.120 --> 00:17:05.679
first month of any crate if you guys enjoyed this video you might

00:17:03.040 --> 00:17:11.120
also enjoy oh maybe a lower capacity but higher performance one new new wanix

00:17:08.400 --> 00:17:14.959
server one experiment the rollout for it freaking couldn't have gone any better

00:17:13.039 --> 00:17:17.839
actually and that thing is flipping fast we're gonna have a playlist where you

00:17:16.319 --> 00:17:23.880
can watch all the new wanick stuff can you make playlists let's make the playlist it's going to be called the

00:17:20.480 --> 00:17:23.880
wanik three