WEBVTT 00:00:00.000 --> 00:00:01.500 Well, hello YouTube 00:00:01.500 --> 00:00:08.420 We have a bit of a problem today on this section of the moving, but we've been moved in for months moving vlog 00:00:09.960 --> 00:00:11.400 Something is going on with the server 00:00:11.400 --> 00:00:17.400 and we haven't been able to work on a project for more than like 30 minutes at a time before the server crashes and 00:00:17.480 --> 00:00:22.440 Our computers all freeze and then we're all sad because we can't work on them. Most of the sh** we do is on the server 00:00:22.880 --> 00:00:26.520 Well, I'm doing I'm actually doing some writing right now because I can do that 00:00:26.520 --> 00:00:30.980 I'd love to be working on my next video. Anything that doesn't need the server we can do now 00:00:30.980 --> 00:00:34.260 No, that's not much, but it always seems to go down 00:00:34.260 --> 00:00:40.560 Yeah, at the worst when there's nothing else to do. No kidding, but you know YOLO you only 00:00:41.420 --> 00:00:43.710 Liao once 00:00:45.270 --> 00:00:48.030 See let's see the stress that Linus is going through right now 00:00:48.030 --> 00:00:53.510 I'm only getting about 25 minutes per second, 30 minutes per second 00:00:53.510 --> 00:00:56.890 It's probably gonna crash like while you're doing this 00:00:57.990 --> 00:00:59.070 Yes 00:00:59.070 --> 00:01:01.390 How do we fix servers? How do you fix it? 00:01:02.050 --> 00:01:04.470 Tell Linus he will fix it 00:01:05.290 --> 00:01:07.290 That's your go-to. Yeah 00:01:07.810 --> 00:01:17.260 Whether you're running a small business or a 00:01:17.600 --> 00:01:24.220 One billion dollar or even multi-billion dollar enterprise Rackspace has your dedicated storage environments covered 00:01:24.300 --> 00:01:27.280 Check out the link in the video description to learn more 00:01:27.800 --> 00:01:28.610 All right 00:01:28.610 --> 00:01:29.990 So here's the situation 00:01:29.990 --> 00:01:35.170 Wonix server over the course of the last couple of days has been spontaneously going offline 00:01:35.670 --> 00:01:41.490 And turning off in spite of my best efforts to turn it back on and 00:01:41.870 --> 00:01:46.990 Complete the backup that I'm in the middle of trying to do to our new unraid vault 00:01:47.780 --> 00:01:49.780 While I was standing in front of it. I 00:01:50.960 --> 00:01:53.110 observed 00:01:53.110 --> 00:01:55.830 One of my raid controllers giving up the ghost 00:01:56.050 --> 00:02:00.210 So as a reminder this server is running three raid fives 00:02:00.670 --> 00:02:04.450 Striped together in Windows of a total of 24 SSDs 00:02:04.570 --> 00:02:07.010 So if one of the raid fives drops out in time 00:02:07.110 --> 00:02:14.110 Entirely all the data is gone only about 10% of the backup that I was just in the middle of 00:02:14.730 --> 00:02:16.390 remaking is 00:02:16.390 --> 00:02:18.520 saved 00:02:18.520 --> 00:02:19.870 so 00:02:19.870 --> 00:02:21.870 It's time to 00:02:22.610 --> 00:02:26.200 Investigate. All right. So here's wonix server 00:02:26.920 --> 00:02:33.740 So far troubleshooting steps that I've tried you never want to you never want to rebuild something like this if there's a possibility 00:02:33.860 --> 00:02:38.920 You're gonna have to go to a data recovery service because that can make it much much worse 00:02:38.920 --> 00:02:39.500 so 00:02:39.500 --> 00:02:46.300 In terms of troubleshooting steps, I tried transplanting it into another case so that I could use a different 00:02:47.800 --> 00:02:53.320 SATA backplane that didn't work. I tried a different power supply a better power supply 00:02:54.040 --> 00:02:55.040 That didn't work 00:02:55.040 --> 00:02:58.140 None of that fixed it and I even went as far as to put in 00:02:58.480 --> 00:03:02.700 Another LSI raid card that I had and try to import the array 00:03:02.740 --> 00:03:08.880 But while it did detect my drives all of them as unconfigured good and a foreign array 00:03:08.880 --> 00:03:11.480 It was not able to import it 00:03:11.680 --> 00:03:17.720 So there is some good news there though while I'm getting firmware errors kicked out by this card right here when I try to boot 00:03:18.120 --> 00:03:21.640 All the drives are detected by another card 00:03:21.640 --> 00:03:26.060 So hopefully it didn't write too much garbled data to the array 00:03:29.080 --> 00:03:31.980 Okay, so this is basically what I've been doing for the last 00:03:32.800 --> 00:03:35.860 14 hours is sending emails contacting different 00:03:36.640 --> 00:03:38.640 Data recovery services 00:03:39.140 --> 00:03:40.580 There's some that are local 00:03:40.580 --> 00:03:46.340 there's some that are not local, but I'm not ruling those ones out. In fact, right 00:03:46.340 --> 00:03:52.580 now the most likely solution looks like WeRecoverData.com. They've got some 00:03:52.580 --> 00:03:58.200 custom tools that they've created that will allow them to SSH into the system 00:03:58.200 --> 00:04:05.830 and actually potentially recover the missing RAID 5 and then the 00:04:05.830 --> 00:04:11.930 other two RAID 5s and assemble them all together and export them as one 00:04:11.930 --> 00:04:17.530 gigantic pile of data to one of our servers, all without me actually having 00:04:17.530 --> 00:04:22.600 to send the drives away, which would be pretty ideal. Now obviously an approach 00:04:22.600 --> 00:04:26.500 like that would not work in the case of physical damage to the drives, but 00:04:26.500 --> 00:04:32.240 because it is only a RAID controller issue, they're saying, hey, there's a shot 00:04:32.240 --> 00:04:34.720 at this, so let's give it a try. 00:04:34.720 --> 00:04:36.000 So I just 00:04:36.000 --> 00:04:44.140 downloaded their remote recovery client thing here. So right now I'm waiting for 00:04:44.140 --> 00:04:51.760 their custom Linux-based tool to load on a bootable external SSD so that they can 00:04:51.760 --> 00:05:00.030 SSH into the server. I'm not having a good couple days. Right now I can't get 00:05:00.030 --> 00:05:10.690 the utility to detect my USB drive. It's called tech support. Oh bloody hell, I just 00:05:10.690 --> 00:05:11.290 figured it out. 00:05:11.310 --> 00:05:16.370 This is Linus calling, by the way. I just realized I have to run the WRD disk 00:05:16.370 --> 00:05:25.180 image as administrator. You guys should put that in the documentation. It never 00:05:25.180 --> 00:05:29.240 fails. This is why it's a good idea to call tech support, because the second you 00:05:29.240 --> 00:05:32.180 call them, you'll solve the problem on your own. 00:05:32.180 --> 00:05:45.520 Alright, so in theory we now have a bootable drive. Okay, so step one is 00:05:45.520 --> 00:05:53.340 getting this unnecessary extraneous server out of the way. I'm grabbing a UPS to use. 00:05:53.500 --> 00:06:03.260 Now, in a perfect world, I would have a motherboard or an HBA card, a host bus 00:06:03.260 --> 00:06:09.140 adapter card, that could allow me to plug in all 24 of the drives for them to do 00:06:09.140 --> 00:06:14.400 their data recovery magic on. But what we're gonna have to settle for is having 00:06:14.400 --> 00:06:19.060 eight of them plugged into the motherboard at a time as each RAID 5 is 00:06:19.060 --> 00:06:24.640 rebuilt. RAID cards do all kinds of funny, funny nonsense and they don't give other 00:06:24.640 --> 00:06:25.260 software 00:06:25.260 --> 00:06:30.960 direct access to the drives at a bit level in some cases. So we need to remove 00:06:30.960 --> 00:06:38.270 all these drives and plug them in directly to the motherboard. Okay, now it 00:06:38.270 --> 00:06:43.220 should boot to that, in theory. Let's just make sure all the drives are detected in 00:06:43.220 --> 00:06:47.880 the BIOS and everything. Oh, that's a problem. I need to pull out the other 00:06:47.880 --> 00:06:50.560 RAID controllers as well, otherwise they're gonna be looking for their 00:06:50.560 --> 00:06:57.360 drives and I don't have them powered up right now. Okay. Oh, actually that doesn't 00:06:57.360 --> 00:06:59.500 look very good. 00:06:59.700 --> 00:07:14.580 DCI-E port errors. What? So let's make sure all of our drives are even showing 00:07:14.580 --> 00:07:32.220 up. Uh-oh. That is extremely worrying. Oh, that is extremely worrying. Oh, that's not 00:07:32.220 --> 00:07:38.140 good. That means potentially three of the drives in a RAID 5 are dead, which means 00:07:38.140 --> 00:07:40.770 this data is not coming back. None of it. 00:07:40.770 --> 00:07:44.840 Not this particular RAID? 00:07:44.840 --> 00:07:46.160 No, none of it. 00:07:46.160 --> 00:07:46.660 None of the... 00:07:48.100 --> 00:07:49.100 But I thought we have three RAID 5s. 00:07:49.100 --> 00:08:00.350 None of it will be coming back if we lost three drives from one of the RAID 5s. 00:08:00.350 --> 00:08:06.070 So let's try moving things around. I've never tested the SATA ports on this board. 00:08:06.070 --> 00:08:11.090 It's possible three of them are dead, however extraordinarily unlikely that 00:08:11.090 --> 00:08:21.390 would be. Five, six. Okay, we've got six now. Okay, that gives some hope. I'm just 00:08:21.390 --> 00:08:26.210 moving SATA ports around. I was just gonna say right now I'm even having difficulty 00:08:26.550 --> 00:08:34.200 in this system to post. So I'm at a whole new level of concern. Yeah, I'll let you 00:08:34.200 --> 00:08:42.030 know. I'll send an email. Okay. So I'm at the point now where I don't want to put the 00:08:42.030 --> 00:08:48.430 drives on this system. Let's go with this one. I didn't like all those PCI Express errors 00:08:48.430 --> 00:08:53.950 that the bootable USB was kicking out. I don't like that some of these drives aren't showing 00:08:53.950 --> 00:08:58.940 up. I'm starting to wonder if that's what corrupted the LSI card. This royal pain in 00:08:58.940 --> 00:08:59.940 the ass. 00:08:59.940 --> 00:09:06.730 A thousand things I can think of that I would rather be doing right now. Okay, I got seven 00:09:06.730 --> 00:09:13.690 right now. Really? Yeah. Wow, maybe it was bad PCIe. Linus speaking. Well, I can tell 00:09:13.690 --> 00:09:18.710 you what's happening so far is I put it on the system that I was running the RAID card 00:09:18.710 --> 00:09:26.750 and the drives in and that baby started spitting out PCIe errors all over the place. So I got 00:09:26.750 --> 00:09:32.170 everything pulled out of that system and I have plugged all the drives now into a different 00:09:32.370 --> 00:09:34.950 disk bench and I'm trying to see because I wasn't even getting all the drives showing 00:09:34.950 --> 00:09:40.120 up. Two, three, four, five, six, seven, eight. Okay. Hey, you guys are on the phone for the 00:09:40.120 --> 00:09:44.100 magic moment where all eight drives are detected by a new motherboard. So I'm beginning to 00:09:44.100 --> 00:09:48.100 think there may be a motherboard issue that caused the firmware on that LSI controller 00:09:48.100 --> 00:09:52.300 to corrupt in the first place. So I'm actually pressing enter and I am booting up to your 00:09:52.300 --> 00:10:01.020 USB and it is loading correctly on this. I think that board is dead. Okay. Well, that's 00:10:01.020 --> 00:10:02.640 I don't know if that makes it worse. 00:10:03.460 --> 00:10:08.300 Probably does, doesn't it? You can tell me. I can take it. It says waiting up to 60 more 00:10:08.300 --> 00:10:14.520 seconds for network configuration. Good timing with the follow-up call. If you called one 00:10:14.520 --> 00:10:17.880 minute earlier, I've been cursing you for dialing my number. So I have to answer my 00:10:17.880 --> 00:10:21.960 phone because I was in the middle of thinking only five of my drives were being detected. 00:10:21.960 --> 00:10:25.660 You guys know what you're doing, right? I had a local shop that I was going to physically 00:10:25.660 --> 00:10:30.180 take it to and they basically, they were like, they kind of freaked out when I said I was 00:10:30.180 --> 00:10:33.020 having someone use their remote tool. They were like, well, unless these guys really 00:10:33.020 --> 00:10:33.440 know what they're doing. 00:10:33.460 --> 00:10:36.940 That's pretty dangerous. And I was like, okay, well I'll, I'll check with them. I'll make 00:10:36.940 --> 00:10:41.680 sure they, they know what they're doing. So, so you guys know what you're doing. So basically 00:10:41.680 --> 00:10:46.600 they're explaining that they're going to virtually Mount the volumes. So we're not doing any 00:10:46.600 --> 00:10:53.900 writing to my discs. Um, so even in the event that we cannot recover it by this means, uh, 00:10:53.900 --> 00:11:05.390 that still leaves other options open to us. Okay. They're in. Okay. Well, that's, that's 00:11:05.390 --> 00:11:09.930 very wonderful to hear, but I'm trying not to get too excited right now. They sound pretty 00:11:09.930 --> 00:11:15.090 confident. This is like the ultimate roller coaster right now. So to put this in the appropriate 00:11:15.090 --> 00:11:23.010 context for the viewers right now, one X server has several in progress projects stored on 00:11:23.010 --> 00:11:27.550 it that do not have a backup anywhere else, including a fully shot channel, super fun 00:11:27.550 --> 00:11:33.410 that involved a thousand dollars in equipment rental, um, including, uh, lots of footage 00:11:33.410 --> 00:11:39.930 from Linus tech tips videos. Like it is going to be a huge, huge, devastating loss for us. 00:11:39.930 --> 00:11:45.450 To lose this. I mean, it's got a lot of our, our templates for editing, uh, editing videos 00:11:45.450 --> 00:11:50.030 for, for scripting templates for employee reviews, like all kinds of stuff. Like this 00:11:50.030 --> 00:11:55.550 is our main working server. No, the offsite backup server has not ever been built yet. 00:11:55.550 --> 00:12:00.510 The vault was the backup server. If I ever have to like act in a, in a video where I 00:12:00.510 --> 00:12:04.890 have to look for Lauren, I'm going to think back to this moment. Okay. So I do need to 00:12:04.890 --> 00:12:09.170 reboot it once in order to add that eight terabyte drive. So anyway, right. Okay. Thank 00:12:09.170 --> 00:12:09.910 you very much, gentlemen. 00:12:09.930 --> 00:12:18.900 I hope to speak to you, uh, with good news very soon, 12 SATA connectors. Ah, ah, ah. 00:12:18.900 --> 00:12:26.140 Okay. So let's make sure everything is showing up 1, 2, 3, 4, 5, 6, 7, 8 of those are boot 00:12:26.140 --> 00:12:34.700 device and our eight terabyte recovery media. We are ready to rock. Okay. So within about 00:12:34.700 --> 00:12:38.380 10 minutes, they contacted me back. They said, okay, yeah, we're ready to have all the drives 00:12:38.380 --> 00:12:44.030 in there. So that means we are going to have to do some janky ass. 00:12:44.090 --> 00:12:53.670 Right now. So basically what you're looking at here is these drives are going to be powered 00:12:53.670 --> 00:12:59.310 off this power supply with a jumper. These cards and all these drives are going to be 00:12:59.310 --> 00:13:03.840 powered off of this rig. So now we can power all those drives without powering up this 00:13:03.840 --> 00:13:05.500 motherboard or any of that nonsense. 00:13:05.500 --> 00:13:13.220 Okay? So we have a grand total of 25 drives connected to this test bench. 16 of which 00:13:13.220 --> 00:13:14.580 are running in Bay's. 00:13:14.580 --> 00:13:19.580 of this enclosure and eight of which are spread out here. 00:13:21.340 --> 00:13:22.480 So there we go. 00:13:22.480 --> 00:13:24.060 There's one of my LSI controllers. 00:13:24.060 --> 00:13:26.300 There's its eight drives. 00:13:26.300 --> 00:13:28.040 There's my other one. 00:13:28.040 --> 00:13:34.920 Whoa, where are your virtual drives? 00:13:34.920 --> 00:13:37.020 I think I remember a troubleshooting step 00:13:37.020 --> 00:13:40.320 where I tried swapping all the drives to different bays 00:13:40.320 --> 00:13:42.120 where I was trying to see if it was the back plane 00:13:42.120 --> 00:13:43.000 or the cables. 00:13:43.860 --> 00:13:48.940 Wow, panic moment there, but it's okay. 00:13:48.940 --> 00:13:54.500 So now we should see two virtual drives here on the screen. 00:13:54.500 --> 00:13:56.560 That's one set. 00:13:56.560 --> 00:13:59.570 Show me the second set. 00:13:59.570 --> 00:14:06.910 Oh, I thought we lost another RAID 5 there. 00:14:06.910 --> 00:14:09.530 Okay, it's good. 00:14:09.530 --> 00:14:11.470 Feeling good. 00:14:11.470 --> 00:14:14.970 Reality TV ain't got nothing on IT work. 00:14:14.970 --> 00:14:17.570 Show me all the devices. 00:14:17.570 --> 00:14:19.730 Two RAID adapters, one eight terabyte drive, 00:14:19.730 --> 00:14:21.430 one, two, three, four, five, six, seven, 00:14:21.430 --> 00:14:23.740 eight Kingston drives. 00:14:23.740 --> 00:14:25.540 Boom. 00:14:25.540 --> 00:14:26.380 Okay. 00:14:26.380 --> 00:14:27.000 I will let... 00:14:27.000 --> 00:14:30.260 the data recovery specialists know. 00:14:30.260 --> 00:14:31.100 All right. 00:14:31.100 --> 00:14:32.340 So all that's left now then I think, 00:14:32.340 --> 00:14:35.280 I got in touch with them and I asked if we can put 00:14:35.280 --> 00:14:37.700 a 10 gigabit network card in 00:14:37.700 --> 00:14:41.060 so we can accelerate the offloading of all of our files. 00:14:41.060 --> 00:14:42.360 So all we're waiting for now 00:14:42.360 --> 00:14:44.220 is for them to reboot the machine 00:14:44.220 --> 00:14:47.400 and set me up with a network share that I can access 00:14:47.400 --> 00:14:50.900 and fingers crossed, 00:14:50.900 --> 00:14:52.720 just start pulling off all the footage 00:14:52.720 --> 00:14:54.710 and well, everything else. 00:14:54.710 --> 00:14:55.530 All right. 00:14:55.530 --> 00:14:56.950 So check this out here, around here. 00:14:56.950 --> 00:14:58.590 So I've got the instructions 00:14:58.590 --> 00:15:02.590 for how to access our data. 00:15:02.590 --> 00:15:08.050 So I go into the Tritium share 00:15:08.050 --> 00:15:09.990 and there it is. 00:15:09.990 --> 00:15:13.410 Bunch of EULAs, a bunch of stuff. 00:15:13.410 --> 00:15:18.410 We've got what looks like the file structure. 00:15:18.410 --> 00:15:20.110 Let's test it. 00:15:20.110 --> 00:15:22.410 How about one that I, 00:15:22.410 --> 00:15:24.570 that we haven't finished releasing yet? 00:15:24.570 --> 00:15:26.870 Like something from the, the melee battle here. 00:15:26.870 --> 00:15:29.210 Let's just, let's watch it. 00:15:29.810 --> 00:15:31.300 Hmm. 00:15:31.300 --> 00:15:36.860 Okay. XA footage for sure. 00:15:36.860 --> 00:15:48.420 Oh, okay. 00:15:48.420 --> 00:15:49.860 Here we can copy one of these. 00:15:49.860 --> 00:15:52.000 Let's copy one of these clips to my local machine 00:15:52.000 --> 00:15:54.870 and see if that helps. 00:15:54.870 --> 00:15:55.710 No. 00:15:55.710 --> 00:16:00.500 Oh boy. 00:16:00.500 --> 00:16:01.340 Let's have a look. 00:16:01.340 --> 00:16:03.220 I wonder if everything's even here. 00:16:03.220 --> 00:16:05.720 Like I don't even see the Linus tech tips folder. 00:16:05.720 --> 00:16:09.890 One and two are missing. 00:16:09.890 --> 00:16:12.050 Useful applications is empty. 00:16:12.050 --> 00:16:14.860 That should be full of things. 00:16:14.860 --> 00:16:20.510 Okay. Well, I guess we'd better get in touch with them. 00:16:20.510 --> 00:16:21.510 So thanks for watching. 00:16:21.510 --> 00:16:26.510 Subscribe, follow all that good stuff and see you next time. 00:16:26.510 --> 00:16:28.250 I just got an email back from them. 00:16:28.250 --> 00:16:31.670 Please stand by addressing your emails with the engineer. 00:16:31.670 --> 00:16:34.890 It's possible the RAID definitions were changed 00:16:34.890 --> 00:16:36.930 from one reboot to the next 00:16:36.930 --> 00:16:39.390 because of drive letter assignments in Linux. 00:16:39.390 --> 00:16:41.230 It's 26, so it's 26 drive limit. 00:16:41.230 --> 00:16:45.310 We have, I think we have more than 26 devices in there. 00:16:45.310 --> 00:16:46.650 I got another email back. 00:16:46.650 --> 00:16:49.760 Linus, we recreated the block devices. 00:16:49.760 --> 00:16:50.640 Please go ahead and check the videos in context. 00:16:50.640 --> 00:16:52.840 That you were looking at again. 00:16:52.840 --> 00:16:56.120 No way. 00:16:56.120 --> 00:16:57.500 Oh, the suspense. 00:16:59.360 --> 00:17:01.970 I'm not enjoying this. 00:17:01.970 --> 00:17:02.810 Is nothing there? 00:17:02.810 --> 00:17:05.930 I'll let them know the chair's empty again. 00:17:05.930 --> 00:17:10.860 This is just like the wildest roller coaster ever. 00:17:10.860 --> 00:17:11.840 I don't even, yeah. 00:17:11.840 --> 00:17:14.590 I don't even have anything else to say actually. 00:17:14.590 --> 00:17:16.230 It's almost funny. 00:17:16.230 --> 00:17:19.520 I hope to some of you it's funny. 00:17:19.520 --> 00:17:21.400 Here's the email I got 17 minutes ago. 00:17:21.400 --> 00:17:22.560 I was stuck on a call. 00:17:22.560 --> 00:17:24.140 We got everything remounted. 00:17:24.140 --> 00:17:25.800 So you can now go ahead and view the data. 00:17:25.800 --> 00:17:26.960 Once more. 00:17:26.960 --> 00:17:30.990 This is the moment. 00:17:30.990 --> 00:17:32.230 Do we not have a two? 00:17:32.230 --> 00:17:33.990 I don't think we ever had a two. 00:17:33.990 --> 00:17:35.650 Oh, okay. 00:17:38.290 --> 00:17:41.130 Okay, so let's go to that Channel Super Fun video 00:17:41.130 --> 00:17:42.570 that we were looking at. 00:17:42.570 --> 00:17:44.010 Yes, yes, Swagway jousting. 00:17:44.010 --> 00:17:51.300 Okay, and it was the delivery. 00:17:51.300 --> 00:17:54.870 I'm getting like tingling. 00:17:54.870 --> 00:17:56.690 Okay, okay, you gotta check the source files though 00:17:56.690 --> 00:17:58.070 because that was what we know was corrupted. 00:17:58.070 --> 00:17:59.470 Okay, okay, okay, okay. 00:17:59.470 --> 00:18:01.970 So untranscoded footage. 00:18:01.970 --> 00:18:10.260 XA, they did it. 00:18:10.260 --> 00:18:13.030 It's back. 00:18:13.030 --> 00:18:15.090 My God. 00:18:15.090 --> 00:18:16.310 It's back, here's another file. 00:18:16.310 --> 00:18:17.150 It's back. 00:18:17.150 --> 00:18:20.640 Do we have everything? 00:18:20.640 --> 00:18:22.640 In theory, yes. 00:18:22.640 --> 00:18:24.420 Really? 00:18:24.420 --> 00:18:27.330 Holy . 00:18:27.330 --> 00:18:29.840 Oh. 00:18:29.840 --> 00:18:31.980 I think it's finally over. 00:18:31.980 --> 00:18:32.820 Woo hoo. 00:18:34.910 --> 00:18:37.900 That is fantastic. 00:18:37.900 --> 00:18:42.270 Hey guys, guess what happened with the recovery? 00:18:42.270 --> 00:18:43.450 We got everything back. 00:18:43.450 --> 00:18:45.450 Oh, thank goodness. 00:18:45.450 --> 00:18:46.290 Woo hoo. 00:18:46.290 --> 00:18:49.810 Like it's just been such a stressful few weeks 00:18:49.810 --> 00:18:53.600 and that was just such a huge, huge thing. 00:18:53.600 --> 00:18:58.040 All of our pitches and proposals and stuff are on that server. 00:18:58.040 --> 00:19:02.100 Okay, Wanik's back. 00:19:02.100 --> 00:19:02.940 Bully? 00:19:02.940 --> 00:19:03.780 Really? 00:19:03.780 --> 00:19:06.120 Everything is back as far as I can tell. 00:19:06.120 --> 00:19:08.900 I have played back video files. 00:19:08.900 --> 00:19:11.180 They are not corrupted. 00:19:11.180 --> 00:19:13.560 Wanik is officially back. 00:19:13.560 --> 00:19:17.680 Swagway jousting footage for the melee battle should be fine. 00:19:17.680 --> 00:19:21.320 And we'll have a better backup scheme in the future, I promise. 00:19:21.320 --> 00:19:22.440 That is all. 00:19:22.440 --> 00:19:23.440 Yay. 00:19:23.440 --> 00:19:24.440 Yay. 00:19:24.440 --> 00:19:25.440 Yay. 00:19:25.440 --> 00:19:26.440 Video shot. 00:19:26.440 --> 00:19:30.440 We should physically print all of our videos, every frame of every video on that paper. 00:19:30.440 --> 00:19:31.440 I don't think so. 00:19:31.440 --> 00:19:33.120 Did you hear the good news? 00:19:33.120 --> 00:19:34.120 That Wanik's back? 00:19:34.120 --> 00:19:35.120 Wanik is back. 00:19:35.120 --> 00:19:37.120 Yay for hiring other people to do our jobs. 00:19:37.120 --> 00:19:41.060 No, I don't think it's back, but it is. 00:19:41.060 --> 00:19:42.060 It's back. 00:19:42.060 --> 00:19:43.540 What are you doing? 00:19:43.540 --> 00:19:45.620 I'm just letting everyone know that Taren, it's back. 00:19:45.620 --> 00:19:46.620 The server is back. 00:19:46.620 --> 00:19:47.620 It's back. 00:19:47.620 --> 00:19:48.620 The server is back. 00:19:48.620 --> 00:19:49.620 Okay? 00:19:49.620 --> 00:20:03.120 So it's not always that our sponsors tie so perfectly into our content, but today it happened. 00:20:03.120 --> 00:20:07.900 Today's sponsor is Rackspace, the top tier managed cloud computing company. 00:20:07.900 --> 00:20:11.720 They pride themselves on best in class service across all platforms. 00:20:11.720 --> 00:20:17.020 They've got over 300,000 customers in 120 countries with 10 worldwide data centers. 00:20:17.020 --> 00:20:23.060 They've got Red Hat, Cisco, Microsoft, VMware certifications, and all of that amounts to, 00:20:23.060 --> 00:20:27.820 whether you're running a small business or a billion dollar enterprise, whatever your 00:20:27.820 --> 00:20:33.560 needs are in terms of capacity storage or flash-based high performance storage, they 00:20:33.560 --> 00:20:42.180 can take care of it without you going gray or bald because you did something wrong and 00:20:42.180 --> 00:20:46.560 screwed up a backup and went and lost a RAID array or whatever else. 00:20:46.560 --> 00:20:52.060 They've got dedicated storage to meet your performance, security, network capacity, and 00:20:52.060 --> 00:20:53.060 compliance needs. 00:20:53.060 --> 00:20:57.780 Everything from direct attached storage, so that gives you the flexibility and scalability 00:20:57.780 --> 00:21:03.000 of just a simple, okay, let's attach some drives to this thing, it's redundant, cool, 00:21:03.000 --> 00:21:08.340 off you go to the races, to SAN, so that's high availability and reliability, fully redundant 00:21:08.340 --> 00:21:13.500 for business, to even NAS with support for demanding workloads like virtualization, file 00:21:13.500 --> 00:21:15.000 sharing, and rich media. 00:21:15.000 --> 00:21:20.700 In fact, their NAS stuff can scale up to 20 petabytes of capacity. 00:21:20.700 --> 00:21:23.000 They've got public cloud and private cloud options. 00:21:23.000 --> 00:21:28.000 As well, you can get your own server, a scalable private cloud in the data center, in your 00:21:28.000 --> 00:21:33.060 data center, in their data center, and it's all supported by Rackspace and VMware. 00:21:33.060 --> 00:21:38.000 They call their support fanatical because these people are available 24 hours a day, 00:21:38.000 --> 00:21:44.640 seven days a week, 365 days a year, and they've got industry leading service level agreements, 00:21:44.640 --> 00:21:46.700 both managed and intensive. 00:21:46.700 --> 00:21:51.840 So if you need dedicated storage, they got you covered. 00:21:51.840 --> 00:21:52.840 Go to rackspace.com. 00:21:52.840 --> 00:21:58.800 de to learn more, and not go through what I did. 00:21:58.800 --> 00:22:04.050 I just, yeah, I don't really have anything to say 00:22:04.050 --> 00:22:05.050 Thanks for watching guys. 00:22:05.050 --> 00:22:09.090 If you just like this video, then hit the dislike button, I guess. 00:22:09.090 --> 00:22:10.090 But come on. 00:22:10.090 --> 00:22:12.710 This is about as real as it gets around here. 00:22:12.710 --> 00:22:15.090 If you liked the video, hit that like button. 00:22:15.090 --> 00:22:20.510 Get subscribed, maybe even consider checking out our Amazon affiliate, instructions for 00:22:20.510 --> 00:22:21.510 how to use it. 00:22:21.510 --> 00:22:22.370 Whenever you buy stuff there, instructions are up there. 00:22:22.370 --> 00:22:23.470 Buy and share with worksheets. 00:22:23.470 --> 00:22:23.970 That's it. 00:22:24.310 --> 00:22:28.070 cool shirt like this one or even giving us a monthly contribution through our 00:22:28.070 --> 00:22:31.330 forum which gives you a little contributor badge now that you're done 00:22:31.330 --> 00:22:34.110 doing all that stuff hey maybe you want to check out that Channel Super Fun 00:22:34.110 --> 00:22:39.250 video that we just discovered is back and that'll definitely be worth your 00:22:39.250 --> 00:22:45.480 while we joust with each other on swagways it's pretty awesome so see you 00:22:45.480 --> 00:22:47.960 next time