WEBVTT 00:00:00.320 --> 00:00:08.400 So, on today's episode of Holy, 00:00:04.240 --> 00:00:11.440 we have Oh, wow. This is really heavy. 00:00:08.400 --> 00:00:15.759 This is I'm fairly certain the most 00:00:11.440 --> 00:00:18.880 expensive thing I have ever unboxed. 00:00:15.759 --> 00:00:21.279 This is the pedibyte project. And what 00:00:18.880 --> 00:00:27.359 is a pedibyte? Well, a pabyte is a thousand 00:00:25.439 --> 00:00:34.490 terabytes. a thousand terabytes of storage. 00:00:38.000 --> 00:00:45.360 I by Power and MSI's new lineup of gaming laptops feature Intel 7th 00:00:42.800 --> 00:00:50.000 generation Core i7 processors. Check them out at the link below. 00:00:48.079 --> 00:00:57.360 So, I guess this is where we start. I mean, what does a pedabyte look like 00:00:53.600 --> 00:01:01.520 physically? Well, we've got one box. 00:00:57.360 --> 00:01:04.879 Then we got two boxes. And actually, 00:01:01.520 --> 00:01:08.560 look at this. There's another box 00:01:04.879 --> 00:01:13.920 inside. I hope I don't break the table. 00:01:08.560 --> 00:01:17.840 Inside all these boxes are 100 00:01:13.920 --> 00:01:19.920 10 terbte Seagate Enterprise 00:01:17.840 --> 00:01:24.640 Heliumfilled drives. 00:01:21.680 --> 00:01:31.360 100 of them. So 100* 10 for those of you who attended the same math school that I 00:01:26.479 --> 00:01:33.200 went to is 800 terb. 00:01:31.360 --> 00:01:38.159 And you'll get that joke a little bit better later. Um, so how do you 00:01:36.159 --> 00:01:41.920 transport 100 hard drives? I was actually 00:01:39.840 --> 00:01:47.600 legitimately curious myself because I've I've never had 100 hard drives delivered 00:01:44.159 --> 00:01:50.240 to me before. The answer is apparently 00:01:47.600 --> 00:01:53.840 via couriers that don't even need labels on the outsides of the boxes. These 00:01:52.399 --> 00:01:59.840 really don't seem like they're doing a lot. I mean, they sprinkled some peanuts 00:01:56.640 --> 00:02:03.159 on there. Good job. If it's broken, I'll 00:01:59.840 --> 00:02:03.159 forgive them. 00:02:03.280 --> 00:02:12.640 You know what? I am just going all like 00:02:08.000 --> 00:02:14.160 Tarzan on this thing. There we go. 00:02:12.640 --> 00:02:17.360 I mean, the thing about hard drives is you you pick up one of them off the 00:02:16.000 --> 00:02:24.400 table, they don't really seem that heavy. We pick up 20 of them. They start 00:02:20.400 --> 00:02:26.400 to get pretty heavy pretty fast. 00:02:24.400 --> 00:02:33.080 So, we actually probably have to get like 00:02:28.879 --> 00:02:33.080 each of these boxes open. 00:02:35.040 --> 00:02:41.840 Now, how did they end up with this random mish mash of packing materials? 00:02:40.160 --> 00:02:56.000 Let's see how many different types of packing material we can find. 1 2 3 4 5 00:02:48.800 --> 00:03:02.120 6 7 8 9 10 00:02:56.000 --> 00:03:02.120 ah uh uh 10 packing materials. 00:03:02.959 --> 00:03:09.480 Okay, see this one all has the same packing material in it. 00:03:12.239 --> 00:03:20.360 So, here it is. This 00:03:16.720 --> 00:03:20.360 is what's inside. 00:03:23.040 --> 00:03:28.000 More packing material. 00:03:26.640 --> 00:03:33.360 I mean, they're hard drives. They're kind of fragile. This all makes sense. 00:03:29.920 --> 00:03:36.959 But here we go. 00:03:33.360 --> 00:03:39.280 Oh, yes. So, I guess now then is a good 00:03:36.959 --> 00:03:46.319 opportunity to talk about what drives we're using. These are Seagates 00:03:42.080 --> 00:03:48.879 Enterprise Capacity V6 heliumfilled 00:03:46.319 --> 00:03:54.319 drives and we're using them for a number of reasons. So number one is these are 00:03:52.000 --> 00:04:01.200 in the same series of drives as what we've used in the past in both our vault 00:03:57.599 --> 00:04:03.439 as well as our offsite backup server but 00:04:01.200 --> 00:04:09.120 with some technological advancements. So, since we built the original 00:04:05.439 --> 00:04:11.760 long-term archive vault, Newton Server, 00:04:09.120 --> 00:04:17.120 Seagate has gone from 6 terabytes to 10 terabytes on their maximum capacity 00:04:14.319 --> 00:04:24.160 drive. And number two is that thanks to their heliumfilled enclosures, they are 00:04:19.759 --> 00:04:25.840 more efficient than ever before. 00:04:24.160 --> 00:04:30.000 There's also a degree of trust that comes with a choice like this. and using 00:04:28.320 --> 00:04:34.479 something that has served us incredibly well in now both the vault and our 00:04:32.000 --> 00:04:39.360 off-site backup uh was a fairly easy decision to make. But of course, a bunch 00:04:36.560 --> 00:04:43.040 of drives is just a bunch of drives until you actually put it into a 00:04:41.440 --> 00:04:48.240 machine. So here representing the Storinator that 00:04:46.160 --> 00:04:52.320 I will actually be using since it's upgraded with a better drive mounting 00:04:50.080 --> 00:04:58.320 mechanism and LCD and all that good stuff is my old Storinator 45 drive 00:04:56.160 --> 00:05:03.680 edition that I use as like a bench server now. So why we like Storinators? 00:05:01.759 --> 00:05:09.280 Couple of reasons. Number one is they're actually reasonably affordable for like 00:05:06.960 --> 00:05:15.919 machines that can hold anywhere from 45 to 60 drives. Number two is that we have 00:05:14.000 --> 00:05:20.880 found them, again it comes down to stuff we've used in the past, incredibly 00:05:17.520 --> 00:05:24.320 reliable. So instead of having um a SAS 00:05:20.880 --> 00:05:26.960 or SATA expander setup with backplanes, 00:05:24.320 --> 00:05:33.120 they actually directly attach every single drive to the HBA cards in the 00:05:30.080 --> 00:05:35.759 system through dedicated cables. So it 00:05:33.120 --> 00:05:57.360 just means there's less junk to go wrong. 00:05:57.360 --> 00:06:04.960 and and they're in except for one small problem. Lionus, hold on a second. Even 00:06:02.560 --> 00:06:09.440 if this was the 60 drive model and it had an entire additional bank of drives, 00:06:07.600 --> 00:06:13.280 you would still have an entire countertop full of drives over here. 00:06:12.080 --> 00:06:20.240 What's the deal with that? How are you going to actually have one pabyte of storage on the server? Great question. 00:06:17.280 --> 00:06:24.960 So, unfortunately, we love Unrade, but we can't use Unrade for this project 00:06:22.479 --> 00:06:30.319 because right now, Unrade is limited to only one array per system and 30 drives 00:06:28.080 --> 00:06:35.840 per array. So, we had to look beyond that. It looks like what we're going to 00:06:31.919 --> 00:06:38.800 be using is two of the 60 drive models 00:06:35.840 --> 00:06:44.000 each with 50 drives in it give or take and we're going to be using some flavor 00:06:40.319 --> 00:06:46.720 of Linux either CentOS or Ubuntu running 00:06:44.000 --> 00:06:52.240 ZFS. So we're going to divide up all the drives into VDEVs which is a sort of 00:06:49.440 --> 00:06:56.639 software RAID. Then on top of that we're going to be running something called 00:06:53.680 --> 00:07:00.960 Gluster FS. Gluster FS has some really cool advantages. Number one it's free 00:06:58.479 --> 00:07:05.280 and open source. And number two, it allows us to take these multiple servers 00:07:03.440 --> 00:07:10.960 and effectively make them transparent to every other 00:07:07.520 --> 00:07:13.840 computer on the network as one machine. 00:07:10.960 --> 00:07:18.080 Pretty cool. Advantage number two, and this is really neat, is that it has 00:07:15.360 --> 00:07:22.720 native support for SSD tiering. So, I don't have them yet, but 00:07:21.120 --> 00:07:27.680 okay, I can't lift you up to show you where they're going to go. Wow, this is 00:07:24.160 --> 00:07:33.120 heavy. Um, but Seagate is also sending 00:07:27.680 --> 00:07:35.199 two of their 7 plus terabyte PCI Express 00:07:33.120 --> 00:07:41.680 Nitro cards that are going to sit in each of these machines and act as a 00:07:37.440 --> 00:07:45.199 high-speed, high IOPS cache in front of 00:07:41.680 --> 00:07:47.440 the mechanical drives. The only real 00:07:45.199 --> 00:07:54.400 disadvantage of this approach is the usual disadvantage that comes with any 00:07:50.080 --> 00:07:58.639 type of RAID. We are not going to get 00:07:54.400 --> 00:08:00.240 the full one pabyte. It looks like the 00:07:58.639 --> 00:08:05.520 configuration I'm going to use is going to leave us with about 800 terabytes, 00:08:03.440 --> 00:08:08.800 which is like I'm starting to think I'm not even going 00:08:06.960 --> 00:08:13.280 to bother doing this project at all because 00:08:10.879 --> 00:08:18.000 I mean what's what's the point of even continuing at that point? Only 800 00:08:15.680 --> 00:08:21.840 terabytes of storage. Okay, sorry. I regained my composure. 00:08:19.680 --> 00:08:25.120 Um, the last question that some of you probably have about this project, why on 00:08:23.599 --> 00:08:29.520 earth do you guys need a pedabyte of freaking storage? And the answer is 00:08:27.440 --> 00:08:32.240 pretty simple. We archive everything. Uh, should we archive everything? I 00:08:31.199 --> 00:08:36.800 don't know. I'll leave that up to you. But I'm a bit of a data packrat. So, we 00:08:34.560 --> 00:08:42.000 archive absolutely everything. And we recently upgraded to the 8K camera that 00:08:39.680 --> 00:08:49.040 you guys are watching this super sharp, super crisp footage on. So, we have 00:08:44.720 --> 00:08:50.959 filled up our 170 TBTE archive machine. 00:08:49.040 --> 00:08:57.519 We needed to upgrade to something and this looked like a super well relatively 00:08:55.040 --> 00:09:02.080 cost-effective way to handle it and one that allows us to not dramatically 00:08:59.839 --> 00:09:06.480 change our infrastructure. We can expand it in the future by sliding in more 00:09:04.640 --> 00:09:11.200 storage full of drives. They could even have different drives. You just have to 00:09:08.160 --> 00:09:12.959 configure your bricks differently. or 00:09:11.200 --> 00:09:17.839 moving further into the future, we may look at tape archive for anything that 00:09:15.200 --> 00:09:22.399 doesn't sit on the on the hot server, the spinners. 00:09:19.760 --> 00:09:26.800 So there you have it. This is pedabyte project. 00:09:24.000 --> 00:09:33.360 Let me do that differently. This is pedibyte project. 00:09:29.920 --> 00:09:36.160 It slices, it dices, it takes apart your 00:09:33.360 --> 00:09:41.920 devices and puts them back together. It's the ProTek Toolkit from iFix It, 00:09:39.200 --> 00:09:45.279 and I absolutely love it. I love endorsing this thing because you 00:09:43.360 --> 00:09:50.320 basically cannot go wrong with it. It includes their 64-bit driver kit, which 00:09:48.080 --> 00:09:55.040 means that it runs on Windows Vista. 64-bit. Just kidding. It's actually 00:09:52.000 --> 00:09:58.399 screwdriver bits, not computer bits. And 00:09:55.040 --> 00:10:01.279 a whole bunch of other fantastic tools 00:09:58.399 --> 00:10:06.000 as well, including their extension for the screwdriver, their ESD safe 00:10:03.600 --> 00:10:10.640 tweezers, their reverse tweezers, their plastic opening tools, their suction 00:10:07.920 --> 00:10:14.320 cups, their Jimmy pry tool, their their metal spudgers, basically everything you 00:10:12.560 --> 00:10:18.640 could want. And it all has a lifetime warranty. So head over to 00:10:16.160 --> 00:10:24.240 ifixit.com/Linus. Use their great guides to repair and fix 00:10:21.360 --> 00:10:28.560 your devices and use code Linus to save five bucks on your very own ProTek 00:10:26.880 --> 00:10:31.279 toolkit. So, thanks for watching, guys. If you 00:10:30.079 --> 00:10:36.320 just like this video, you know where that button is. But if you liked it, hit the like button, get subscribed. We have 00:10:34.320 --> 00:10:39.680 t-shirts. We have a place where you can buy all this stuff. We've got all that 00:10:38.160 --> 00:10:42.399 linked. We've got our community forum. All that's good stuff. Now that you're 00:10:41.200 --> 00:10:47.360 done doing all those things, you're probably wondering what to watch next. Check out our latest video over on 00:10:44.880 --> 00:10:52.000 Channel Super Fun. Trying to do my outro faster. I realize I'm not helping my 00:10:49.200 --> 00:10:52.000 case right now.