WEBVTT

00:00:00.000 --> 00:00:03.439
okay hold on oh god

00:00:05.200 --> 00:00:12.880
after being gravely disappointed when some of my fellow youtubers showed off

00:00:09.280 --> 00:00:16.160
their 30 to 60 000

00:00:12.880 --> 00:00:18.240
jellyfish network storage devices i set

00:00:16.160 --> 00:00:22.080
out with exactly the same budget to build something that could absolutely

00:00:20.000 --> 00:00:27.359
run circles around the thing now given that we could afford ssds for

00:00:25.039 --> 00:00:31.840
what they charge for hard drives it wasn't surprising when we

00:00:29.599 --> 00:00:36.399
fried their jellyfishies but for some reason apparently people are still

00:00:34.000 --> 00:00:42.000
buying enough of these jellyfish things that owc recently purchased lumaforge

00:00:39.920 --> 00:00:47.600
the company that makes them did we not make our point people do you have any

00:00:44.719 --> 00:00:53.520
idea how much money we could have saved if we didn't go full stupid and build

00:00:49.840 --> 00:00:56.719
the thing purely from solid state drives

00:00:53.520 --> 00:00:56.719
the answer is

00:00:57.760 --> 00:01:03.280
45 000 that's right

00:01:00.879 --> 00:01:07.040
on this table is everything we need to build a machine that is better than the

00:01:04.960 --> 00:01:14.159
jellyfish in just about every possible way and costs one fifth as much

00:01:11.360 --> 00:01:18.000
so let's fry the jellyfish once and for all and we're gonna do so with the help

00:01:15.760 --> 00:01:21.119
of our friends over at pulseway big thanks to paul sway not only for

00:01:19.439 --> 00:01:25.280
sponsoring this video but for building such fantastic remote management and

00:01:23.280 --> 00:01:28.479
monitoring software with pulseway you can manage your whole organization's it

00:01:27.200 --> 00:01:33.200
infrastructure on the go with their mobile apps and even create and deploy

00:01:30.960 --> 00:01:37.400
custom scripts to simplify your job check them out at the link below

00:01:44.400 --> 00:01:50.320
i'm sure you're thinking lioness you can't possibly make something for

00:01:48.399 --> 00:01:55.439
one-fifth of the price without some pretty big compromises on the hardware i

00:01:52.720 --> 00:01:58.799
mean when it comes to a gaming pc yeah you can save a few hundred bucks

00:01:56.880 --> 00:02:03.200
building your own over getting someone to do it for you but if you try to cut

00:02:01.040 --> 00:02:07.759
eighty percent of your budget you're going to end up with something like this

00:02:05.280 --> 00:02:12.959
where is it going really impressive i'm stuck no professional would use that

00:02:10.399 --> 00:02:17.680
well you're wrong excuse me wrong so very wrong lumaforge

00:02:15.760 --> 00:02:22.560
has a few different models but we're going to be targeting their tower slash

00:02:19.840 --> 00:02:27.599
rack models specifically because well partly they're the most ridiculous

00:02:24.640 --> 00:02:32.160
and also partly we like the idea of rack mounting storage and we actually intend

00:02:29.760 --> 00:02:37.040
to use this thing in the long term so we're going to replicate the 240

00:02:34.400 --> 00:02:41.440
terabyte rack model with the optional boost package we'll talk about what that

00:02:39.120 --> 00:02:47.599
marketing nonsense actually means later for our case we've gone with istar usa's

00:02:44.000 --> 00:02:50.239
e4 m24 hd which includes even more drive

00:02:47.599 --> 00:02:55.280
slots than the rack or tower jellyfish and should fit the rest of our hardware

00:02:52.560 --> 00:02:59.840
nicely one challenge though is that lumaforge is not very forthcoming about

00:02:57.519 --> 00:03:03.840
the specific components of their systems lest somebody google the part numbers

00:03:01.920 --> 00:03:06.720
and figure out how hard they are being pleased

00:03:05.040 --> 00:03:10.080
but there are some things that we know from last time around and some others

00:03:08.800 --> 00:03:15.920
that we can glean from their product pages first off lumaforge's big selling point

00:03:13.519 --> 00:03:20.319
is that it's all direct attached you just grab your network cable plug it

00:03:18.800 --> 00:03:26.400
directly into the machine you want to edit on and bam it works just like usb

00:03:23.360 --> 00:03:28.640
with no network switch required even for

00:03:26.400 --> 00:03:34.799
multiple users but being the reasonable person i am

00:03:32.799 --> 00:03:39.360
i just can't fathom why anybody would want a setup where you have more than

00:03:36.879 --> 00:03:44.879
say two or three people editing off of the same box and you don't just run a

00:03:41.840 --> 00:03:48.080
network switch microtech even has a 12

00:03:44.879 --> 00:03:50.159
port 10 gig switch for only 500

00:03:48.080 --> 00:03:56.799
so for the amount that i'm paying for lumaforge's special sauce here i could

00:03:52.959 --> 00:03:58.959
buy a pallet of 10 gig switches but okay

00:03:56.799 --> 00:04:03.680
i'm gonna put myself in the shoes or sandals as it were of the person who

00:04:01.519 --> 00:04:08.720
thinks that that's an ideal workflow and i'm going to grab two Intel quad port 10

00:04:06.480 --> 00:04:15.040
gigabit network cards that gives us a total in this system of 10 10 gig ports

00:04:12.400 --> 00:04:18.400
for storage lumaforge uses zfs a file system and volume manager wrapped into

00:04:17.040 --> 00:04:23.759
one that they've got running inside centos a Linux based operating system

00:04:21.359 --> 00:04:28.320
like last time though we are taking a different route and we're gonna go with

00:04:25.440 --> 00:04:34.000
truenas core formerly known as freeness which also uses zfs as its file system

00:04:31.520 --> 00:04:38.160
but has a more user-friendly management interface based on their specs page it

00:04:36.160 --> 00:04:45.040
appears that lumaforge is using groups or v-devs of 10 drives running raid z2

00:04:42.800 --> 00:04:51.120
what that means is each group of 10 drives in your jellyfish can sustain

00:04:48.880 --> 00:04:55.520
two drive failures before you actually lose any data and since they have 20 12

00:04:53.600 --> 00:04:59.520
terabyte drives on the terabyte model that we're trying to

00:04:56.800 --> 00:05:04.720
replicate we could suffer up to four total drive failures before we actually

00:05:01.759 --> 00:05:10.400
lost anything that is as long as they failed two in each group if we lost them

00:05:07.680 --> 00:05:15.360
like this all right we'd be plumb out of luck on all the

00:05:13.440 --> 00:05:20.080
data on these drives we're not too worried about that though

00:05:17.199 --> 00:05:24.320
because seagate sent over 22 of their exos 12 terabyte enterprise drives which

00:05:22.880 --> 00:05:29.039
boasts two and a half million hours meantime between failure low power

00:05:26.320 --> 00:05:34.880
consumption and excellent resistance to vibrations from nearby drives which

00:05:32.160 --> 00:05:38.720
there's gonna be uh a few of them also the five-year warranty is a nice touch

00:05:37.039 --> 00:05:44.000
that's a seagate part number yeah but hp enterprise model hp

00:05:40.720 --> 00:05:47.120
enterprise now funny story we would have

00:05:44.000 --> 00:05:49.680
actually used seagate's ironwolf pro

00:05:47.120 --> 00:05:54.800
consumer grade nas drives but at the time of filming these exos enterprise

00:05:52.400 --> 00:05:58.800
drives were actually cheaper so uh

00:05:56.000 --> 00:06:04.319
weird flex seagate but okay now according to lumaforge's

00:06:00.880 --> 00:06:07.680
website the performance boost package

00:06:04.319 --> 00:06:09.080
doubles the stock 128 gigs of RAM so

00:06:07.680 --> 00:06:15.120
we're gonna be running 256 gigs of 3200 megahertz crucial

00:06:12.720 --> 00:06:20.319
registered ecc memory in eight channel mode that should give us a really nice

00:06:17.440 --> 00:06:24.240
balance of cost and performance and we haven't had a single stick of this stuff

00:06:22.160 --> 00:06:28.319
fail in our last handful of deployments so we absolutely love it so far

00:06:27.120 --> 00:06:34.479
as for the ingest capacitor well that's a fancy

00:06:31.120 --> 00:06:37.280
name for a right cache which zfs calls a

00:06:34.479 --> 00:06:41.120
slog this limited amount of faster solid-state storage prevents the hard

00:06:39.199 --> 00:06:45.360
drives in the array from getting bogged down when data is getting written to the

00:06:43.280 --> 00:06:48.960
machine at the same time that somebody is trying to edit off it like for

00:06:47.280 --> 00:06:53.680
example when you're ingesting footage off of your cameras now we don't know

00:06:51.120 --> 00:06:58.400
how big the drive they use is but we figured a two terabyte NVMe drive from

00:06:56.240 --> 00:07:02.960
saverin would be plenty for most ingest workflows given that camera media larger

00:07:01.039 --> 00:07:07.680
than that is pretty unusual as for read caching you see i'm holding two drives

00:07:04.639 --> 00:07:09.840
here zfs utilizes something called arc

00:07:07.680 --> 00:07:14.960
which is a portion of the system memory that acts as a live cache for frequently

00:07:12.800 --> 00:07:20.240
or recently used files problem is when it comes to media work

00:07:17.199 --> 00:07:24.080
they're full of large files and you can

00:07:20.240 --> 00:07:26.319
have enormous projects so even our 256

00:07:24.080 --> 00:07:29.199
gigabytes of RAM could be easily filled up

00:07:27.199 --> 00:07:34.400
thankfully there's a special feature called level two arc that allows us to

00:07:31.680 --> 00:07:39.759
add a second NVMe drive that will be a well slower than memory but still faster

00:07:37.520 --> 00:07:44.000
than hard drive caching layer before you start reading directly off of the

00:07:41.360 --> 00:07:47.599
spinning rust lumaforge doesn't actually include this in their systems but since

00:07:46.080 --> 00:07:52.400
the motherboard that we chose has an extra m.2 slot and we have

00:07:50.560 --> 00:07:56.080
lots of budget left over to play with we figured hey

00:07:54.160 --> 00:08:00.560
how many times do you live however many times you live it's not

00:07:58.240 --> 00:08:05.120
enough times to risk downtime or data loss due to a power supply failure

00:08:02.960 --> 00:08:10.560
that's why we actually deviated from the jellyfish's original design

00:08:07.520 --> 00:08:14.319
this right here is the twins pro 700

00:08:10.560 --> 00:08:16.800
watt from fsp and it is super cool

00:08:14.319 --> 00:08:22.240
like the 1000 watt consumer grade unit that lumaforge uses it fits in any

00:08:19.039 --> 00:08:26.240
standard atx case but unlike that one it

00:08:22.240 --> 00:08:29.840
can sustain a complete failure of one of

00:08:26.240 --> 00:08:32.240
the two redundant power supply modules

00:08:29.840 --> 00:08:36.719
that goes into the back like so another nice benefit of this thing is

00:08:34.320 --> 00:08:40.640
that it actually allows you to plug into two independent power sources if you had

00:08:39.200 --> 00:08:46.399
say for example a ups and a

00:08:43.440 --> 00:08:49.360
just direct into mains power one really you should just have two

00:08:47.600 --> 00:08:52.480
ups's though and the best part about this thing is

00:08:50.880 --> 00:08:57.920
that we were really concerned about noise but it ended up being well not

00:08:55.440 --> 00:09:02.000
quiet but reasonable enough that you could have it in an open office space

00:08:59.680 --> 00:09:04.240
and it wouldn't be a huge nuisance now

00:09:02.800 --> 00:09:08.160
obviously if you're going to have your jellyfish fryer like

00:09:06.000 --> 00:09:12.399
on your desk right next to your head you might want to choose something else but

00:09:10.160 --> 00:09:16.560
never fear because you can afford literally the most expensive enthusiast

00:09:14.800 --> 00:09:21.440
power supply on the market with all the money you saved and then you can go get

00:09:18.959 --> 00:09:25.200
it gold plated at a local shop one optional upgrade would be to pull

00:09:23.120 --> 00:09:29.519
out these hot swappable sleds and replace the sunon fans that ship with

00:09:27.200 --> 00:09:32.959
this case something like a Noctua industrial ppc might have a longer

00:09:31.839 --> 00:09:38.000
lifetime but for our purposes it's not like sunon

00:09:35.680 --> 00:09:41.600
is a bad fan manufacturer and given that we're going to be putting it in a server

00:09:39.360 --> 00:09:45.040
rack anyway we're just not that concerned about noise and the

00:09:43.120 --> 00:09:48.959
convenience of having these plug right into these little daughter boards that

00:09:46.399 --> 00:09:52.480
go into the drive back plane is pretty good one thing that's a little funky

00:09:50.640 --> 00:09:58.000
about our configuration is that this power supply has fixed cables on it and

00:09:55.360 --> 00:10:02.320
unfortunately it's only got i think like two molex connectors well we need a

00:10:00.560 --> 00:10:06.080
total of uh 10 for all of the hard drives that we

00:10:04.560 --> 00:10:11.839
have installed in this thing so what we'll be doing is adapting SATA to molex

00:10:09.600 --> 00:10:16.000
because it's the only connector on here that's still got 5 volt built into it

00:10:14.079 --> 00:10:19.040
otherwise we'd love to use the pci express connectors which you don't need

00:10:17.360 --> 00:10:24.320
in a storage server now that doesn't sound great but as long

00:10:22.160 --> 00:10:28.560
as you pay attention to the max amperage that these cables and these connectors

00:10:26.079 --> 00:10:32.800
are rated for it should be okay as for the rest of the machine we chose AMD's

00:10:30.560 --> 00:10:37.200
epic platform due to its excellent price performance and feature set which is

00:10:35.519 --> 00:10:41.600
basically everything specifically we've gone with a 24 core

00:10:39.680 --> 00:10:47.680
epic 7302p cooled by Noctua's adorable little nhu9

00:10:44.880 --> 00:10:52.880
sp3 which is one of the only coolers specifically engineered to cover the

00:10:49.680 --> 00:10:55.920
massive heat spreader on an epic CPU

00:10:52.880 --> 00:10:58.160
for our board we've chosen asrock rack's

00:10:55.920 --> 00:11:02.000
epic d82t this board is great for a number of

00:10:59.600 --> 00:11:05.360
reasons i mean just look at all that expansion

00:11:03.360 --> 00:11:09.920
it's freaking crazy have i mentioned by the way how much i

00:11:07.040 --> 00:11:14.480
love epic because thanks to epic we've got 128

00:11:11.680 --> 00:11:19.760
total lanes of pci express to tap in that gives us all the slots we need for

00:11:17.279 --> 00:11:25.440
our hba which is what we plug all our drives into our 10 gigabit mix including

00:11:22.959 --> 00:11:30.000
the two that are already on board our dual m.2s for those caching drives i

00:11:27.760 --> 00:11:35.200
mentioned before it's even got two mini sas hd ports over here that gives us

00:11:32.560 --> 00:11:40.959
another eight drives so we only need a 16 drive host bus adapter in our case an

00:11:37.920 --> 00:11:43.040
lsi 9305 16i check this out too it's

00:11:40.959 --> 00:11:47.519
even got a couple of oculink ports so that is eight more lanes of pci express

00:11:45.920 --> 00:11:50.560
down there this thing's awesome i think the only

00:11:49.200 --> 00:11:56.000
thing that could make it better is if it was pci express gen 4 which

00:11:53.279 --> 00:11:59.040
naturally asrock rack has it's just not something that we would get a

00:11:56.959 --> 00:12:02.800
performance benefit from so we are using the gen 3 one this is fun while i was

00:12:01.279 --> 00:12:06.880
plugging power into the motherboard i noticed that this power supply has a usb

00:12:05.279 --> 00:12:10.959
connector coming out of it turns out that fsp has a little tool it

00:12:09.279 --> 00:12:14.160
only runs in Windows unfortunately so we can't use it but they have a little tool

00:12:12.480 --> 00:12:18.560
that allows you to monitor temperatures fan speeds all that kind of cool stuff

00:12:16.399 --> 00:12:23.360
just off of a usb header for boot drives we used a couple of

00:12:20.160 --> 00:12:25.680
kingston 240 gig ssds and you can use

00:12:23.360 --> 00:12:29.200
basically anything for this the one thing i'd recommend is having two of

00:12:27.600 --> 00:12:34.240
them so that in the event of a boot drive failure you have a live backup of

00:12:30.959 --> 00:12:35.279
it ready to go okay not backup but copy

00:12:34.240 --> 00:12:38.720
there and i guess that's pretty much it isn't

00:12:37.519 --> 00:12:48.720
it yeah we're just gonna put up do it 24 cores 256 gigs of RAM 10 10

00:12:44.800 --> 00:12:51.760
gigabit network ports 24 drives 700

00:12:48.720 --> 00:12:54.399
watts of redundant power and a mirrored

00:12:51.760 --> 00:12:58.160
240 gig boot drive for one-fifth of the price now we just got to boot this puppy

00:12:56.959 --> 00:13:01.680
up ah um

00:13:00.160 --> 00:13:05.200
there's probably another cable oh look at another cable we've already installed

00:13:03.680 --> 00:13:08.959
trunas so we're just going to boot right up to that if you guys want to know how

00:13:06.959 --> 00:13:12.160
to install it patrick from serve the home did a great guide last time we

00:13:10.800 --> 00:13:16.720
collaborated so we're going to link that in the video description now that's a

00:13:14.000 --> 00:13:20.800
lot of network interfaces look at that 10 10

00:13:18.240 --> 00:13:23.279
that's 10 gigabits 10

00:13:21.600 --> 00:13:27.279
gig we could put them all together for 100 maybe yeah we could

00:13:24.880 --> 00:13:31.200
100 gigabytes would be a big nicktoon that would be way smarter if we just put

00:13:29.360 --> 00:13:35.839
100 gigabit nick in here and then a switch and still had lots of money left

00:13:33.040 --> 00:13:39.839
over but whatever we're direct attached now that we're fired up we're in that

00:13:37.440 --> 00:13:42.560
beautiful little web ui actually this has improved a lot since the last time i

00:13:41.440 --> 00:13:48.040
looked at it there's all those interfaces there's those power supplies

00:13:48.800 --> 00:13:53.600
by far the loudest fans in the system are the ones in the power supplies

00:13:52.160 --> 00:13:57.600
because they're just these little tiny things but if you're not into it

00:13:56.160 --> 00:14:01.680
just swap it out for something else because hey you built it you designed it

00:13:59.839 --> 00:14:05.440
you can do it the way you like so we've got two groups of 10

00:14:03.680 --> 00:14:09.199
and then like i showed you guys earlier we could lose

00:14:06.880 --> 00:14:13.120
up to four before we actually lose any data and in the true nash dashboard of

00:14:11.120 --> 00:14:17.279
course we can see our two raid z2s both with 10 drives and on the bottom we have

00:14:15.279 --> 00:14:21.519
our log drive as well as our cache drive so cache would be the level two arc and

00:14:19.440 --> 00:14:25.680
then log is the s log like we mentioned before

00:14:22.800 --> 00:14:31.839
i like calling it a slog slog it's gotta slog through those

00:14:28.560 --> 00:14:31.839
index entries

00:14:32.320 --> 00:14:38.240
all right slog through them what we're going to show you guys now because

00:14:36.560 --> 00:14:41.920
really the main point of this isn't how to set up truenose we want to show you

00:14:40.079 --> 00:14:47.120
guys how we're going to do the direct attach special magic that jellyfish

00:14:44.560 --> 00:14:50.480
ships so we've got a test system right here on our test cart that's got a 10

00:14:48.720 --> 00:14:53.839
gig network card in it we're gonna go ahead and run the oh my god that's not

00:14:52.160 --> 00:14:58.480
screwed into anything did you just pull it out uh well i didn't not pull it out

00:14:56.399 --> 00:15:02.079
you didn't not pull it out what does that even mean

00:15:00.320 --> 00:15:06.240
it means we're about to find out smart guy ah

00:15:04.160 --> 00:15:11.680
it's probably fine it's hot swap right you tried PCIe hot top right ah

00:15:08.800 --> 00:15:15.440
is that the right HDMI i think so well it was on before oh crap well you

00:15:13.839 --> 00:15:20.240
didn't screw the thing in well it didn't have a thing and we're just trying to do it quickly right here you could just

00:15:18.240 --> 00:15:23.519
move it i wasn't expecting you to just yoink all right i didn't he's a yoinker

00:15:22.320 --> 00:15:28.320
man you just you got to be careful around this well

00:15:26.000 --> 00:15:32.880
Linus tries to fix that um we're on the trunas side and basically all you need

00:15:30.240 --> 00:15:37.600
to do to set up a direct attach setup like the fancy jellyfish software would

00:15:35.279 --> 00:15:40.880
do is essentially just assign an ip address to both interfaces on either

00:15:39.360 --> 00:15:44.480
side and then the computer will facilitate transfer between the two

00:15:42.399 --> 00:15:47.120
machines in what's known as an unrouted subnet there's no router that's

00:15:45.760 --> 00:15:52.959
controlling the packets it's just the systems telling each other where it needs to go so we're in trunas i've set

00:15:50.480 --> 00:15:57.120
up 10.96.0.10 for this computer and we've got to make

00:15:54.560 --> 00:16:00.639
sure our subnet is the same so dash 24 and then on that side we'll do

00:15:58.720 --> 00:16:04.399
10.96.0.20 and you can set these to realistically

00:16:02.320 --> 00:16:08.880
whatever you want click apply there

00:16:06.720 --> 00:16:13.040
test changes oh man trueness has a super nice thing basically when you're doing

00:16:10.639 --> 00:16:17.360
network changes on trinas it will like try them for 60 seconds and if you don't

00:16:15.279 --> 00:16:20.800
confirm it in the dashboard it will just revert back to the way it was you can't

00:16:19.120 --> 00:16:24.000
screw it up and like make it so you have to boot it into recovery mode or

00:16:22.480 --> 00:16:26.880
something to change the settings and then on our Windows computer side we

00:16:25.680 --> 00:16:31.440
have set up the same thing but 10.96.0.20

00:16:28.959 --> 00:16:36.560
same subnet 2552.525 which is the same as 24. we're just gonna click okay there

00:16:34.320 --> 00:16:39.839
close that'll start to do its thing and then we'll just apply on this side

00:16:38.000 --> 00:16:43.279
and we should be pretty much good to go funny story that machine doesn't have

00:16:41.680 --> 00:16:46.800
premiere on it and it's actually faster for us to just go get a longer Ethernet

00:16:44.959 --> 00:16:50.959
cable and plug into one of our editing stations so we're just going to redo the

00:16:48.160 --> 00:16:54.000
ip setup over there one moment please after a quick reboot to get the network

00:16:52.480 --> 00:16:59.519
share remapped properly you can see we've got our j drive which is our

00:16:56.240 --> 00:17:01.920
jellyfish fryer and boom we are video

00:16:59.519 --> 00:17:06.319
editing off of our jellyfish fryer of course what we need to know now is

00:17:04.000 --> 00:17:10.319
how's it handling it and for that naturally we turn to pulseway

00:17:08.160 --> 00:17:14.480
unfortunately pulseway does not yet have support for freebsd based operating

00:17:12.160 --> 00:17:18.559
systems like truenas but we use it for all kinds of server related things here

00:17:16.640 --> 00:17:22.959
at the office and actually even ones that aren't necessarily server related

00:17:20.880 --> 00:17:26.480
with pulseway you can monitor all of your systems through a simple dashboard

00:17:24.799 --> 00:17:30.080
that's available right on your mobile device from here you can see i've

00:17:28.319 --> 00:17:34.559
created a little sandbox account with the machine behind me and one of our

00:17:32.080 --> 00:17:39.200
servers i can monitor everything from system resources like available memory

00:17:36.799 --> 00:17:43.600
or if we're running out of storage to patch policies to even remoting into

00:17:41.600 --> 00:17:47.600
these machines and taking control of them with pulseway you can also create

00:17:45.600 --> 00:17:50.880
custom scripts that simplify your it management and if Windows updates are

00:17:49.760 --> 00:17:54.640
our pain in your butt you can even manage those remotely and schedule them

00:17:52.799 --> 00:17:58.400
as well and if you look around here in the editing den

00:17:56.559 --> 00:18:02.720
we've had to do a lot more remote management than usual with a bunch of

00:18:00.400 --> 00:18:06.240
our staff working from home so try out pulseplay it's available for most

00:18:04.320 --> 00:18:10.080
operating systems including Windows Linux and mac and it's so powerful that

00:18:08.720 --> 00:18:14.160
i'm always learning about new functionality apparently you can use it

00:18:12.160 --> 00:18:18.000
to send a wake wake-on lan ping like a magic packet to one of the machines on

00:18:16.000 --> 00:18:22.000
your network if for whatever reason it's stuck in sleep and you have no way of

00:18:20.559 --> 00:18:28.240
waking it up because you're halfway around the world that's cool stuff even for home users so

00:18:25.840 --> 00:18:33.919
it works great and how much did we pay overall before tax including everything

00:18:31.360 --> 00:18:40.400
we've currently got deployed around 12 000 us dollars that's a lot of money but

00:18:36.720 --> 00:18:42.480
it is nowhere near the 58 000 that

00:18:40.400 --> 00:18:47.440
lumaforge charges for their equivalent and before you ask yes we also accounted

00:18:45.600 --> 00:18:51.919
for the two cold spare drives that aren't even installed that lumaforge

00:18:49.520 --> 00:18:55.600
does include with the jellyfish we could even comfortably step up to

00:18:53.520 --> 00:18:59.760
ironwolf pros which aren't enterprise per se but do have three

00:18:58.000 --> 00:19:03.280
years of data recovery included if you're into that kind of peace of mind

00:19:01.520 --> 00:19:07.919
thing so yeah i can understand the appeal of a

00:19:05.679 --> 00:19:12.240
solution that is all pre-set up for you and has some fancy software for

00:19:09.679 --> 00:19:17.679
connecting to it or whatever but for the price difference you could quite

00:19:14.080 --> 00:19:20.400
literally hire an it person for like

00:19:17.679 --> 00:19:24.240
half a year to spec this thing build it for you deploy it and show you how to

00:19:22.720 --> 00:19:28.720
use it i mean you'd probably have some money left over to send your team on a nice vacation i see how you snuck that

00:19:27.360 --> 00:19:33.760
in there Jake that's that's good that's a good one you know we can't do workation this year as for us this

00:19:32.000 --> 00:19:39.200
machine is destined to become the new local backup server for our NVMe editing

00:19:36.080 --> 00:19:41.440
machine aka new new wanik so wanna go

00:19:39.200 --> 00:19:46.480
check out that video if you haven't seen it yet and go check out pulseway

00:19:44.000 --> 00:19:51.120
pulseway is absolutely fantastic whether you want to simplify your it management

00:19:48.799 --> 00:19:55.440
tasks monitor your servers remote desktop in apply patches pulseway has

00:19:54.080 --> 00:19:59.039
got you covered and you can do everything from their mobile app