WEBVTT 00:00:00.080 --> 00:00:09.480 there's a video coming soon a video about the catastrophic failure of the 00:00:05.960 --> 00:00:13.519 rid array on our 20 terb SSD server code 00:00:09.480 --> 00:00:15.240 name wanck but before we do that video 00:00:13.519 --> 00:00:20.279 why don't we take a moment to introduce to you the newest member of the lonus 00:00:18.039 --> 00:00:29.080 Media Group server family the one I was literally in the process of backing W up 00:00:24.640 --> 00:00:31.960 to when the failure happened meet Clover 00:00:29.080 --> 00:00:31.960 server 00:00:38.960 --> 00:00:45.120 the Logitech g303 features a lightweight design an advanced Optical sensor with 00:00:43.320 --> 00:00:48.719 Delta zero technology for precise tracking and RGB lighting to match your 00:00:47.079 --> 00:00:53.160 setup check out the link in the video description to learn more so I think a 00:00:50.680 --> 00:01:00.280 video about Clover server has to start with the differences between backup and 00:00:57.359 --> 00:01:06.040 redundancy redundancy protects from a hardware failure to an extent but not 00:01:03.039 --> 00:01:08.720 from accidental deletion encryption by 00:01:06.040 --> 00:01:14.759 ransomware vandalism or what I would call catastrophic Hardware failure the 00:01:12.240 --> 00:01:19.320 benefit of redundancy is that it's real time a single drive failure in a raid 00:01:17.240 --> 00:01:24.119 five array for example would allow the business to keep operating completely 00:01:21.400 --> 00:01:29.479 normally and would result in zero lost data as long as it could be offloaded or 00:01:27.040 --> 00:01:36.240 the raate array could be rebuilt with backup you'll only get back whatever was 00:01:32.320 --> 00:01:39.640 in your last periodic backup so Clover 00:01:36.240 --> 00:01:42.439 server wouldn't have prevented any data 00:01:39.640 --> 00:01:47.119 loss from the catastrophic raid failure that recently occurred with wanik server 00:01:44.799 --> 00:01:52.159 one of the raid cards crapped all over the inside of its pants took its pants 00:01:49.320 --> 00:01:56.119 off and started swinging them around what it would have prevented was 00:01:54.040 --> 00:02:00.399 projects that have already been shot weeks ago but not yet edited like this 00:01:58.759 --> 00:02:06.560 video that we had planned for Channel Super Fun from being entirely lost so 00:02:04.799 --> 00:02:11.360 let's take a look at the hardware Clover server is using a quad core xon 00:02:08.720 --> 00:02:17.400 processor on an ASUS p9d M Server Motherboard with 32 gigs of Kingston ECC 00:02:14.599 --> 00:02:22.760 DDR3 memory to give me the best possible stability of course the Redundant power 00:02:19.920 --> 00:02:27.120 supply from istar USA helps with that and the toolless case well okay that's 00:02:25.519 --> 00:02:31.519 just for convenience but the hot swappable Drive bays are really really 00:02:28.959 --> 00:02:36.000 nice ignore that RAID controller you see in this footage that's going to be 00:02:33.040 --> 00:02:39.840 replaced with an LSI HBA and I've also added a 10 GB network card to handle the 00:02:38.080 --> 00:02:44.920 workload alterations that I've made since I built this box for storage I've 00:02:42.480 --> 00:02:49.840 gone with eight of seagate's 8 tbte Enterprise capacity drives these suckers 00:02:47.440 --> 00:02:55.159 do in the neighborhood of 200 megabytes per second and have a rated meantime 00:02:52.159 --> 00:02:57.640 between failure of two million hours 00:02:55.159 --> 00:03:03.200 however whatever their reliability might be in this particular application where 00:03:00.319 --> 00:03:07.879 the intent is to achieve reasonable speed but more importantly 00:03:05.799 --> 00:03:12.760 extraordinarily safe backup remember this will be the only copy of some data 00:03:10.480 --> 00:03:17.840 in the event of wanic pooping itself again I'll be giving up a lot of my 00:03:14.959 --> 00:03:22.920 capacity to the redundancy Gods as well as the speed 00:03:19.599 --> 00:03:24.879 Gods so like most of our servers these 00:03:22.920 --> 00:03:29.319 days the software side of things starts with a fresh install of limex unraid 00:03:27.760 --> 00:03:34.000 which by the way they have sponsored projects of but this isn't one of them 00:03:31.640 --> 00:03:39.080 so we'll be setting up two of our 8 TB drives in what is effectively an 8 tbte 00:03:36.680 --> 00:03:45.959 raid one array configuration and then we'll take the other six in a butter FS 00:03:41.439 --> 00:03:49.120 RAID 10 for 24 tab of redundant storage 00:03:45.959 --> 00:03:50.840 the plan for the 8 tbte array is pretty 00:03:49.120 --> 00:03:56.439 straightforward I'm going to set up a Windows Server 2012 R2 Essentials VM a 00:03:54.680 --> 00:04:00.439 pretty simple process since I don't have to do any video card pass through or 00:03:58.519 --> 00:04:04.799 anything like that if you want to learn more though about unraid VM setup you 00:04:02.400 --> 00:04:09.879 can check out our two Gamers 1 CPU video here I chose Essentials 2012 R2 because 00:04:08.200 --> 00:04:15.319 even though it's quite expensive at about $500 for a license the way it 00:04:13.040 --> 00:04:21.400 handles incremental backup and restore functionality for up to 25 computers is 00:04:18.519 --> 00:04:25.080 really slick and seamless not to mention that if we ever wanted to move to a 00:04:23.040 --> 00:04:29.199 domain setup it includes active directory domain Services although for 00:04:27.080 --> 00:04:32.720 now we're still using a work group so I did have to use this simple workaround 00:04:31.199 --> 00:04:37.880 to enable the nightly backup functionality without requiring the PCS 00:04:35.240 --> 00:04:41.840 to join a domain from there you download and set up the connector software and uh 00:04:40.360 --> 00:04:45.680 this is basically a quick look at the dashboard that allows you to set the 00:04:43.520 --> 00:04:50.479 schedule for nightly backups how long you want to keep them for and change the 00:04:47.960 --> 00:04:56.080 storage destination to the secondary V disk that I created for those backups so 00:04:53.520 --> 00:04:59.759 7 tabt should be lots for our SSD equipped workstations here in the office 00:04:58.160 --> 00:05:05.000 all right then lonus but what about that 24 terab of RAID 10 storage on this 00:05:02.440 --> 00:05:10.280 machine great question I've got two plans for that number one is to use 00:05:07.720 --> 00:05:14.240 Beyond Compare a great piece of software that compares the structure of two 00:05:12.520 --> 00:05:18.840 directories and allows you to set up all kinds of rules for copying One Way 00:05:16.840 --> 00:05:23.240 copying the other way or synchronizing between them and I'm going to use that 00:05:20.600 --> 00:05:26.919 to do incremental synchronizations so this is kind of somewhere between 00:05:24.720 --> 00:05:31.199 redundancy and backup since I plan to run them every 30 minutes or so and I'm 00:05:29.199 --> 00:05:38.280 setting up the relationship so that a deleted file on wanic will be removed on 00:05:34.319 --> 00:05:40.720 the Clover server side as well then 00:05:38.280 --> 00:05:46.759 every night I will set up a backup operation from Clover to the Vault where 00:05:43.919 --> 00:05:52.240 files deleted from wanic and therefore Clover server will not be removed from 00:05:49.600 --> 00:05:57.199 the Vault so we have somewhere to turn to if we accidentally delete something 00:05:54.680 --> 00:06:01.560 major so those operations can both be scheduled simply with Windows Task 00:05:58.960 --> 00:06:06.000 Manager uh super handy and then a monthly or whenever we feel like it 00:06:03.639 --> 00:06:11.080 cleansing of the deleted stuff on the Vault can be done using Beyond Compare 00:06:08.919 --> 00:06:14.800 as well now this isn't a perfect solution but butter FS snapshotting is 00:06:13.080 --> 00:06:18.800 still a ways out so it'll have to do for now and we've got lots of space on the 00:06:16.440 --> 00:06:22.199 Vault so I'm not too worried about it anyway that still only accounts for 00:06:20.400 --> 00:06:27.479 about another 20 terabytes of the space on Clover so we've got 5 terabytes of 00:06:24.599 --> 00:06:32.319 wiggle room for that plan number two I'm going to be leveraging my ceon to use 00:06:30.280 --> 00:06:37.840 that extra space as an off-site backup for my Nas at home using crash plan 00:06:35.479 --> 00:06:41.720 normally I'd actually have to run crash plan from within a Windows environment 00:06:39.840 --> 00:06:46.560 or at least something with a goey but the benefit of using Docker within 00:06:43.919 --> 00:06:50.440 unraid to do it I do plan to do a full video about Docker containers and why 00:06:48.240 --> 00:06:55.800 they're awesome in the future is that if Windows borks up crash plans backing up 00:06:53.240 --> 00:07:00.280 of key files there's not enough leftover space for my whole home array will be 00:06:58.360 --> 00:07:03.919 uninterrupted normally setting up crash plan on a 00:07:02.039 --> 00:07:10.080 headless machine is kind of a nightmare but unraid way is a bit more elegant so 00:07:07.479 --> 00:07:16.160 in summary there's three main points for this video One backups are important two 00:07:13.759 --> 00:07:21.560 create two backups of something that's important during a data migration and 00:07:18.720 --> 00:07:26.479 three more details on the catastrophic raid failure to come speaking of 00:07:24.560 --> 00:07:31.840 catastrophic have you ever been in a situation where you're like I want to 00:07:28.479 --> 00:07:34.319 watch American net but I am not American 00:07:31.840 --> 00:07:39.199 or I am American and I'm not an America well tunnel bear is the easy to 00:07:36.840 --> 00:07:43.319 ous VPN app for that and all kinds of stuff tunnel bear lets you tunnel to 16 00:07:41.879 --> 00:07:47.919 different countries allowing you to browse the internet and use online 00:07:45.520 --> 00:07:52.520 services as if you are in a different country they've got apps for iOS Android 00:07:50.360 --> 00:07:56.199 PC and mac and they've also got a Chrome extension when you pick a country and 00:07:54.400 --> 00:08:00.840 turn tunnel bear on two things happen your connection gets encrypted with AES 00:07:58.120 --> 00:08:04.720 256bit encryption and your public IP address gets switched so that you show 00:08:02.759 --> 00:08:09.319 up as if you are in that other country and they' fixed all the annoying stuff 00:08:06.960 --> 00:08:14.639 that's frustrating about vpns while offering 00:08:10.800 --> 00:08:16.919 500 megabytes of data for free to try it 00:08:14.639 --> 00:08:20.319 out with no credit card required then if you want to upgrade to unlimited data 00:08:18.400 --> 00:08:25.879 you can save 10% by going to Tunnel bear.com LT which is linked in the video 00:08:24.080 --> 00:08:28.919 description all right so thanks for watching guys if this video sucked you 00:08:27.400 --> 00:08:32.320 know what to do but if it was awesome get subscrib hit that like button or 00:08:30.639 --> 00:08:35.479 even consider supporting us directly by using our affiliate code to shop at 00:08:33.719 --> 00:08:39.200 Amazon instructions for how to do that are up there buying a cool shirt like 00:08:37.560 --> 00:08:43.000 this one or with a direct monthly contribution through our community Forum 00:08:41.120 --> 00:08:46.480 you get a cool little contributor badge now that you're done doing all that stuff you're probably wondering what to 00:08:45.120 --> 00:08:50.680 watch next so check out that little button in the top right corner to see 00:08:48.360 --> 00:08:56.720 our video on Channel Super Fun where uh Taran and Luke compete to see who can 00:08:52.680 --> 00:09:00.680 wrap present with drunk goggles on the V 00:08:56.720 --> 00:09:00.680 trust me it's better than it sounds