 Alright, so FreeNAS 11 is out and I want to do a video a little bit in-depth kind of going through the setup process getting the shares going and Basically getting set up now things. I'm not going to cover is specifically going to be the virtual machine inside of it the beehive hypervisor because well, you can't do that in virtual box So I get a This will be a separate video because I got to build a machine for it And I might just be reloading it on my computer our server I might upgrade to this because I feel so far it feels pretty stable I'm gonna go over the settings real quick though of what I built here. So one network adapter and For storage I created just a bunch of virtual disks now obviously this is not at all a real-world setup This is completely just gonna be a demo setup and the reason for that is obviously you don't run FreeNAS It won't run properly in a virtualized environment and all these disks are just well a bunch of virtual disks on one hard drive So they don't really do a lot of good So we're gonna go through the install process actually make sure I got this set up. So FreeNAS and FreeNAS 11 release there we go And we're gonna start walking through the install process Which looks just like the previous versions of FreeNAS Pretty straightforward. I'm not gonna get too in-depth. I'm gonna just cover a couple of quick points inside of here install upgrade Only for demonstration purposes. I went ahead and did this where I have two of them because I do recommend I mean thumb drives are arbitrarily inexpensive And there's not a lot of read rights. I think people worried about failure on these It's mostly read push into memory and then store all the data on the rate array itself But it's so nice to have two of them and it will mirror them if you just select two different USB drives So these little eight gigs represent USB drives now. I did notice this And I haven't done this on any real hardware It detects the USB later So it kind of overwrites on to the screen which is kind of annoying and it offers to do an upgrade install because I'd already Installed this before but I didn't wipe it. So I'm just gonna wipe it now and do a fresh install install format the boot device Proceed with installation. Let me just set the password Boot via BIOS because while we're in virtual box Choose whatever works for you I'm partial to the BIOS ones but kind of depends what your motherboard supports So we're gonna let it run through here almost fast forward all this All right, and it's all set and reboots and we boot up in the free NAS Shut down All right, so we have free nas installed But I canceled the wizard because now I don't care much for the wizard I like to set everything manually, but there are a couple little housekeeping things I do so we're gonna go over here to the advanced and I turn on a couple things which is The autotune which autotune allows the system to put in some extra parameters that fall under tunables Basically, I believe it's like a templating system. It goes. Oh, you have this this and this and we turn these features on you can Auto you can add features yourself and system tunables and custom Things to this most of the machines I've ever built have never had a problem just using the autotune features And I've never tweaked it too far as at the speed and function has been adequate It seems I've never caused any stability problems, but you know mileage may vary You may have some weird hardware configuration that you don't want to do that on but I generally myself have not had a problem with it But start there if you weren't having problems you turn on had problems start with that Next I like to turn on the show counsel messages in the footer Now the nice thing about this is you get this so here are the counsel messages So at any given time you can watch them roll across the bottom and then if you just click on it You can say okay, you know what I'm doing something. I want to see what the counsel messages are because maybe you know Well, even right now I don't feel like pulling up another window or in my case the machine is headless sitting in the back So there's nothing on the screen and you know, you can always go back and look at them But it's kind of nice to have them there Now besides that I do recommend putting a certificate in I'm not going to get in depth on that right now Actually, I had some issues with it with I don't know if it's a Freenance 11 bug or a Chrome bug Chrome doesn't like the self-signed cert on this anymore and Firefox does that's a separate issue. We're gonna focus today on getting your storage set up and getting some sharing done So we're here at the storage now. There's a couple different places. You see things You may have noticed this is just the way Freenance is set up and the new Freenance I think the new interface Makes more sense because there's so much repetition like things across the top and things across the side here But this is you know, the old interface still has all the functionality in it So you can see your storage, but what you may not notice in here is you don't see the system volumes in there And those are Right here, so I went to system boot Storage And then you can see the boot mirror and tell you if those are online or healthy And you get an alert over here if there was an alert if one of those had failed. This is your multiple USB drive boots So that's under system again boot and then status Now there's also a separate grub under boot for the scrub to do the testing of it So you can say you can scrub the boot You can also as I got here create create a new boot and there's a history of all the installs and updates here And this is actually I'll let you keep it rename it clone it or even roll back to Once you can see the initial stall activate versus this is the fault right here And you'll see a whole history of these in a system now. This is my Office one right here and you can see that on reboot. I'm doing this But if I wanted to roll it back, I can actually Activate this one and on reboot it would go back to a previous one You can keep a few previous all depends on how much storage you have available on there To store it on the little thumb drives You do have to go in here after you've done a bunch of updates and delete some of the old updates That is another thing you can do so back to the Free NAS 11 system, so let's get to our storage and as you see we have no disc now You can at this point you can view the disc so you can see all the distance here There's no smart management because these are all virtual drives like I showed you in the beginning It tells you the size of each of the discs It does have an option to wipe them in case you want to wipe them clean before removal for example We can import if there was already a volume on here and you can say import some of these into an existing volume But we're not importing anything and it's like if you set up a new free NAS You load it, but you were pulling the drives out of another free NAS You can actually pull an array and import it in so we're gonna go to volume manager here And we're gonna create our test Volume I really recommend enabling encryption now the reason for this is with the encryption You have the ability to swap a drive out and send it back without worrying about what data is on there Now we keep customer data on the drive So when drives go bad and eventually they will you don't want to have to worry about the data And they're going man, you know, it seems to not read properly, but man I got a lot of data and it's hard to erase But I want to send it in because I had a warranty Use encryption keep peace of mind the encryption does not really add anything in terms of overhead. It's really simple If you use the basic encryption not the passphrase one the passphrase one adds another layer of yet But passphrase in every time it boots But this creates a key file that stored on the USB drive to decrypt the volume on boot that way if you have to Pull any drive out you can send it back in no worries about that now Here's where we choose our rate configurations and there's different options in here We have raid Z raid Z2 raid Z3 just a simple mirror and you can drag the drives around for Different mirroring or striping options. So if we drag them like this are going to be a stripe We do them like this. We can still set up raid Z Because it's a pair of drives each one and this is changing how you mirror the drives Or we can drag them. I think it's like this here So by dragging them around you can choose a different option So this would be so you can create a mirrored set between the drives So one and two in a mirrored set or we can drag them all this way and just let raid Z figure it out I'm really partial to the raid Z Especially like the Z2 now that's going to give you out of this pool It's going to give you to dry failure redundancy because it creates parity data across all the drives Now because it always after a raid works and it's a lot better than hardware raid especially here in 2017 It spreads it across the drives in a much more intelligent way using the ZFS system So if a drive fails we can rebuild it if two drives fail out of this We can rebuild it when you do a raid Z you get more capacity But there's not enough parity created across the drives So if one drive fails you don't lose the array you can rebuild it downside being on the rebuild process You're stressing all the other drives and let's say you have a couple from a similar batch Maybe that one is close to failure because one of them was well now you're stressing it trying to rebuild the array It fails on the rebuild process and maybe you lose your array so all depends on just how critical the data is and how much capacity you're willing to sacrifice for redundancy and Whether or not you went through the trouble to build maybe a second entire array for backing all of this up Or you're backing it up in an off-site server either way these are all some considerations You can read in detail elsewhere about all the different functions of the raid Z and raid Z to but for purposes of this We're just gonna set up as a raid Z to system So now we're gonna add the test volume here All right, it's created and you can see in here some of the things like for example It says it can't load smart. That's because you can't run smart on virtual hard drives. They don't have a smart status Anyways, so we have our volume Now we have the key option here for creating a passphrase if you wanted it more secure We have to put a passphrase to unlock it every time on boot or you can simply just download the key so we provide the root password and Download the key now downloading the key is extra important And it's a very tiny file called gli.key and what this key file is stored on the USB drives If those USB drives go away they fry they die you lose all the encrypted volume That's it. Nothing you can do about it. There's no recovering from it You don't have that key with that data in there. You were not going to be able to recover that so You want to make sure you back that up now I don't know why and it maybe should be a warning message But whenever you're over here on general and you do a save config You know once you get it all set up you can back up all your configuration settings It doesn't back up that key and to my knowledge. They didn't change that in FreeNAS 11 here either So when you do the backups of the system the key still is separate I wish it popped up with the maybe a warning maybe they're changing that in FreeNAS 11 where you can download it But I didn't see anything in the documentation that said that but I know in previous versions of FreeNAS it was not so Here's your volume and here's your data set that's underneath it now for each volume We create a data set now Maybe you can say I just want to dump everything to one data set. It's just me using it I just want to use a big storage server you can do that you can control single data set ideally from a structural standpoint You want to set up individual data sets under this so Here's the test volume and then we're going to create a Data set which was this button down here and this will be our first data set All right, and we're going to go ahead and make this a windows compatible share and we're going to add the data set We're going to add another one now. You can make data sets that are subsets of other data sets But for this we're just going to create another one second data set All right, same thing. We'll make it a windows share Add data set now for each of these data sets for example with the test volume here If I wanted to create a snapshot and I see recursive snapshot It's going to snapshot all the data sets that are under here We're going to cover snapshots after we throw some data on so I can actually show you how they work So here's this data set and for each data set they have their own Permissions so here's the permissions we can set we can set the group and the owner And maybe you want to create a data set because you want to use a set of files And you have another person it wants to use a set of files Then you would then go in here and let's create a user called Tom So we can show you how we set the permissions on there because it's an important part of getting all this set up So users add user Set user Tom All right And hit okay Pretty straightforward now we have a user Tom who we can assign permissions to so we go back over to storage and we're going to give There matter of fact, let's just create a whole separate one again and call it Tom's data set. So we'll Tom's data goes here Tom's data Give me a windows share. So we'll do this There we go your permissions Who's the owner? We're gonna say Tom The users show up at the top. These are some of the built-in accounts I like the fact that it adds the users the top makes a little bit easier. So we're gonna go ahead and Change the owner to Tom So Tom gets to own this data in here. All right now this Allowed us to create a data set called Tom, but there's still not any actual sharing occurring here a couple things We need for that. We need to share first. So we're gonna create a windows share add windows share path Mount test volume Tom's data. There's the share name Now if we want to turn on guest permissions, you can do that which allows guest browsing of it We wanted password permission. So we're just gonna do it this way. It says would you like to start the service? Yes, we would That is the SMB service and we can configure that here. This is where you can rename things for the SMB If there's any specific things you want to set up in here, the defaults are pretty straightforward You do have to change a lot of these things if you're doing an active directory authentication I've done one. I've done a few. They're complicated I've run into some little hiccups with it Maybe I'll do a separate video on it But there's some guides that are really good at step-by-step because it involves creating objects and reverse DNS and PTI records inside the active directory to point to the free NAS box to Basically allow it to handle all the permissions for all the users in active directory It's like I said, I don't do it very often a lot of these are standalone Boxes so there's not not really been as much of an issue to set those up But there's some really good guys right in the form and how to set up free NAS on active directory and they're very accurate All right, so now we have sharing enabled. We've got the service enabled for sharing I also turned on SSH in case everyone SSH into the box So SMB is turned on that's turned on it's checked start on boot now. Let's go to the drive and see if it works Okay, SMB 3.34 Tom's data And we made the username Tom. I have a password on that and Tom has access to it So there we go. There's test another test and It's simple as that. I have a password protected folder that I have access to So how does it look in Windows? Let's cover that real quick Here it is in Windows so we can go here and I typed in slash slash and it's dot 34 Whoops typed in four So slash slash one I two one six eight three dot 34 we go here Put in the password And here we go. Another test and you can see that it works perfectly fine. Now when it comes to security, this is where without active directory you don't get to pull if you had an active directory which there is on this machine When you're trying to edit permissions or create other users. There's no interactivity for that. But you can kind of get the idea. That's how it works. Now you can also in free NAS. Let's shut this down now. Now if you wanted to add other users. That's where the grouping system comes in. I'm not going to get into all the details of the permissions. But in short, you could actually create a security group. There's already a group named Tom, but you call a group called share group. And then you would add each of the users. Let me show you the user directories here. And then you would say you would create that group and then say, okay, other people need to belong to this group and then you can actually group share out a folder that way. And you're letting free NAS handle all the permissions for Windows at that point. It does support it. You can't even set up hierarchies. We've got a couple clients that do that. They've created different groups like accounting and HR and use it without any active directory integration at that point, which is, you know, it's convenient. They only have a couple of people working there. They have a free NAS box. They have it backed up. And it is a fine solution without having to put a Windows machine in there. So they have local storage that they have shared between a couple of people. So Now that we've covered basically how to create a share, let's show you what some of these other ones look like. So here's the one called Tom's data. Now we can create another data set underneath there. So We'll call it nested data. Keep following the Windows pattern here. There's our nested data set. And this is how it shows up in here. So Now we have tests, another test, a couple of folders I created, and we have nested data. This is a data set, not just a folder, but as far as to the way you see it, it just shows up as a folder, which is pretty cool. And the reason why is this is we're going to play with snapshots in this nested data set. Now you can play with it at any level. But let's just start right here to give you an idea. See, the snapshots are a huge important piece of how free NAS works in terms of, you know, being able to do that. Manage data and being able to roll things back and forth. This is a feature and probably a big reason you'd want this. So let's just dump some data here. Oh, I didn't set permissions for this. Go back in here, change it to Tom recursively. All right, now the nested data is owned by Tom. And I pasted some files in here. So let's paste some other randomness in here that I have. All right, so we have a few files in here. And what we're going to do is go to this, and we're going to create a snapshot of this nested data. So create a snapshot. It doesn't need to be recursive because there's nothing else underneath it. So mainly create the snapshot. So then we can take a look. Here's our snapshot that we have no used data, but it refers to 115 megs of data that I have in there. So let's go in and delete the data or let's move it somewhere else. We're going to go new folder. And we're going to take this data, drop it in here, and we're going to delete some of it. So we've completely changed around. We've created a sub folder. We've dropped out some of the data in there. Now we can see that we've used some space. And the reason we've used some spaces because, well, we've changed the files in there. So the snapshot was a reference to how it was then. And we have the option to destroy the snapshot, clone the snapshot or roll back. So let's roll it back. Are you sure you want to roll back? Yep. Let's roll it back. Done. Instant. Very fast. And it's even on large datasets. It rolls back really fast. It's pretty slick. So we go over here and we're going to have to go out, do a quick refresh. It's exactly how we left it. I instantly rolled it back that fast. And that's how snapshots work. Now, if we did it recursively, and let's go back over here to our volumes, and we're going to do the entirety of it. Create a snapshot recursively. Oh, we already have one. So let's go ahead and it gave me an error because I have this one here. Let's go ahead and delete this snapshot because we're trying to recursively create a snapshot that we already have in here. So we got started at the beginning for that one. So go to volumes, test volumes, create snapshot of all the things, create snapshot, and we can go snapshots. And here it did create a recursive one for all of the different volumes that are in here. So this now is a state of each one of these. And you can see how much data was used. And as you move forward, all the data is only stored in here based on the changes it takes. This is what makes snapshot really efficient. Maybe there's not a lot of changes or only some changes. And this is what saves some people from things like Crypto Locker. Because if you get Crypto Lockered and you're using ZFS and you have like a daily snapshot, you're like, Oh, no, I got Crypto Lockered. I can just go back to tomorrow's snapshot. Let me go ahead and destroy this. And the way you do that is you set up periodic snapshot text. So we can actually set it up for the entirety of the volumes so everything gets snapshotted, or we can say just one of them gets snapshotted. And if we do this one here, we say recursive. How long should it last? One week, two weeks. We're going to keep one week of snapshots. When should it occur? What should the interval be? Daily. By default, you can do one every, what was it said at like one hour, but you can change these to every five minutes. So you can literally keep these incremental snapshots ongoing constantly, which is really awesome. This is a really nice feature. And then you say begin time and end time. Only run snapshots during business hours, for example, because, well, that's the only time you're creating data. Or you can say one time a day, and it's going to start at nine, make sure it's over by then, including Saturday, and it'll create these snapshots. And just to keep it clean, we're going to do just the nested data one here. So we're going to play with just that one. But I could do it on any one of these and it doesn't need to be recursive. So we're going to go ahead and do this. Hit OK. It's enabled. Keep snapshot for one week, frequency one day. So then we go over here to snapshots. It's going to take a minute, but it'll eventually start creating the snapshots, and then I'll have a snapshot in there. So pretty slick the way it works. Let's play with a little bit more advanced features on the snapshots themselves. So we're going to go ahead and delete this. So we only have the snapshots we want in here. Go to volumes, go to nested data. And as you can see, we saw the same data in there as we did it. But let's do something a little different. So we're going to dump some more data in here, a couple more random things we threw in here. And then we are going to, let's say, delete this. Well, move into a new folder again. We'll just move just this and that into this folder. Skip. There we go. I actually selected folder. So now we've made some changes. Now this is one of those things that come up. So we go over here to snapshots. Let's create it real quick. So we're going to create the snapshot. And you'll create snapshot. Yep. Then we're going to go back over to here. And we're going to delete a couple things. And we'll just change this one to a different name. So we've done the changes. And let's say you have a user who created a bunch of data. So you don't just want to restore it. You're like, oh, I need to restore the data, but someone else already created a bunch of data in there. This is where snapshots have another feature that's really cool. We can clone the snapshot. So we can say bring me back to the time here. So we'll clone snapshot. So clone must be on the same volume. Tom's data, nested data, manual clone. We're going to call it nested data, manual restore. And we're going to say clone snapshot. I'm going to show you what this does here. We go back over to our volumes. We have yet another nested volume under here. Now what this allowed us to do was create a clone of the data. So we go back here and refresh this. So here's a clone of it. So then I can go through, find these files I wanted, put them back where they belong over here. And then when you're done, you can just destroy the clone. And okay, I'm done with this. I copied the files I wanted. I put them back. I've solved the problem, you know, from the users that created the issue. And then we can just go ahead and destroy the data set. And now, with very simple, without having to do a bunch of restore features, refresh it real quick, we're able to restore things back to normal. So this is one of the advantages of snapshots. You can take these snapshots. And when you have a folder, and you can create maybe a really, you know, high value folder where you know there's a lot of activity that you know this might occur in, this is a really simple way to do it. So you just go here, you set it up to be mainly snapshotting, especially if you have a folder where a lot of people are constantly creating a lot of data. And you know, like, you know, if you have five users using a pool of data in there, but one user screws a bunch of stuff up and needs to go back to earlier, but the other users don't. That's where you can just restore a clone of the system, copy just that person's files back to where they want without disturbing the other users, and then destroy that snapshot. And this is just an, to me, just a beautiful feature of the entirety of the free NAS system being able to do this. Now I'm going to show you our production system real quick. Here's what it looks like as we're adding data in our production system to, for example, for sync thing. I have this set up to do daily snapshots and keep some, I think I got a weekly snapshot, yeah, weekly snapshot on here. And the reason why is when you're using sync thing, it's similar to Dropbox. If I change something on one file, it propagates to my offsite servers and my in-house computers. That being said with that it would propagate badly if I screwed something up. So by keeping snapshots of it, I can just roll back if I needed to, or even clone it and do the same thing I just showed you guys. What's really cool too is you can have filters in here because if you look at this with everything in here, snapshots we've done, we clear these. And we're going to go show all. There's a lot of data in here. So you can filter for date, you can filter for manual snapshots you've done. This is kind of a neat tool to be able to do that. And you can see how much data they're taking up. And if you want to get rid of any of them because like this one takes up too much data, you know, you can get rid of it. Also, you can see the variations in data as it's being copied. So this one here was a 74 megs copied, or down here. And these are sortable. You can sort by, for example, clear this real quick. Sort by how much data was used in the snapshot, sort by how much it was for reference, or the snapshot name. Makes it really handy to find things, sort by available actions, and sort by replication if you're using that. And we'll talk about replication next real quick. So ZFS because of all this wonderful snapshotting features and all these, how do I back it all up? Now someone's asked me, is it just a file when it does this? No, it's function of the file system. So how do you back up all these cool snapshots and everything because you can't just sync them. They're not exactly data. They're functions of the file system. I mean, I'll do a whole other video on this, but you can add a replication task to another ZFS volume. So you can actually create a snapshot of the volume itself. So you set up a periodic snapshot of my test volume. So we can create a snapshot or as periodic ones, we'll just show you real quick. So here's the entire test volume recursively. We only want to keep it, let's say, for one week at a time just like before. Then we go into replication tasks, add a replication task. And what this does is takes that volume data set, the remote volume data set, including you can do all the, what they refer to as a child data sets of it. And you can sync the entirety of the file system, including the status of the snapshot. So if you're in a high availability system, you got really redundant. You don't want your system just backed up. You want all the snapshots backed up so you can roll them back at any time. You can duplicate the entirety of the ZFS system. So the entire file system can be synced up with another NAS, another free NAS box, put them in sync with each other, including all the snapshots. So everything you do on the schedule you set gets duplicated, including all of your snapshots and file sets. And so it's just such a powerful feature in here, and it kind of blows my mind just how well it works. And I haven't really ever had any major chastrophies, but I've had times when I wanted data back and I've never had a problem snapshot. Hit it, boom, restore, create a quick volume set. Or in our example here, how we did it, how we have one that is like a nested data set. You can create another nested data set under this data set and copy the files you wanted without disrupting the intact data. Like I said, for example, you know, when you wanted someone to overwrite one thing. So pretty impressive how that works. So that kind of covers getting started with your first share and how the snapshot works and just kind of an overview of some of the advantages of the ZFS file system, especially, you know, this cool snapshotting system you get and doing data sets or nested data sets or replication. Now, I know a lot of you probably want to know about all the plugins available for a free NAS or some of the, how the jail system works. I may do some separate videos on that. I'm not the most clear on how they're being, you know, handled in here. Now, the Jails is a function of free BSD. It basically is similar to Docker. It's not like a full blown hypervisor, but it creates essentially a jailed version so you can run something within it. We're using this a little bit, but now that they've integrated the whole beehive VM, which is an entire hypervisor, which is you can virtualize the whole operating system and run other operating systems within it. I'm not sure if they're going to be doing away with the jails. Now, the concept was they would have these plugins and they would run inside of jails and everything is sandbox, so to speak. But I don't think there was enough development for it. I know that they tried bringing Docker in for the version 10, the corral version of free NAS. I don't know if they're going to eliminate this or where these are on the path really. But I may do some separate videos on the plugins. I'm definitely going to do a separate one of VM, but I have to build entire machine for that. Now, let's talk about a little bit of the functions of free NAS and how it works, especially the memory. This causes some confusion for people. You can see I've got eight gigs allocated, but I'm not quite using all the eight gigs. And what's going on here is free NAS will use all the memory that you give to it. So we're going to jump over to my production machine again so I can show you a few things. So this machine has 12 gigs of RAM. Free NAS will use pretty much all the memory you can give it. So if I were to put 64 gigs in this machine, even though it doesn't have that big of a storage array, it will fill the memory up with caching information. So especially the read caches, this is what brings people to the controversial thing about ACC memory going. There's a lot of the file system data held in memory. What if the memory gets corrupted? That is a risk. I still have not ever had a problem not using ACC. Do it at your own risk. ACC is a error correction type memory and some people go, you have to have it. Free NAS does CRC checking before each of these writes gets committed. So I feel secure that even if the memory were to somehow have a bit flipped that didn't crash the OS, it magically was able to flip something in memory that didn't cause any other function that the CRC system would fix it before it ever wrote to the file system corrupted. But all comes down to what level of risk are you willing to take with anything. So that's kind of my summary on the memory. What's the level of risk you're willing to take? What's the percentage of it happening? I see less than a 1% chance of that happening so I don't go with the ACC. Back to the memory itself, you will see it utilizing as much memory as it can. So there's a lot of files, there's a lot of reading, writing back and forth. It's going to utilize the memory to put it all into RAM, the entirety of the ZFS, all the different write commits and everything like that to make it more efficient. So if you memory starve one, you get low performance but there's kind of a diminishing return. It will use it but you can't say, I can't go from 32 gigs to 64 gigs and say it's going to double the performance, right? No, not really. There is a point of return and roughly they're saying 1 gig per terabyte of storage and that, you know, it's not really that big of a deal. I do have, like I said, here's the plugins and more specifically the jails. I only have one thing running in the jail and you can see 3.4 is my free NAS box and 3.240 is my clone deploy. One of the interesting things about the jails is they are separate and they get separate IP addresses. Maybe they said I'll do another video specifically on that. So, but you can see in the reporting the partition target, you get ZFS data on here, arc size, which is some of the, this is for the caches. Let's see if we zoom out a little bit. You can see where there were changes made based on data being pulled back and forth when we were dumping massive amounts of data system processes. Depending on what you're using this for, we're only running clone deploy and just clone deploy and ZFS free NAS itself on here. So, the CPU usage is super low on this. Our system is AMD A6. Not any problems with it. It's nothing really beefy. The heaviest, intense thing running and even the load average being high on it is because of the volume of data that we actually back up and synchronize on here. So, we have all of our business data on here and all the server data on here all encrypted and then we synchronize it offsite with another server. So, doing that and we do it on every 15 minute basis, it looks for any new changes and synchronizes them offsite for database changes. So, it does keep the system a slightly higher load, but it's really not, yeah, it's not enough that it's causing any delays or anything like that. And that is what you'll run into. If you do short memory on here, you can run into corruption problems. And if you try to run it with, I don't even, I don't know, we'll run anymore with FreeNAS 11 with less than eight gigs. But one of the concerns you are going to have is it will cause a lot of issues. If the system wait time is because it's swapping between basically a swap file and trying to keep things in memory, you have what they call IO wait times. The IO is constantly waiting on the memory to feed it and you will end up with possible corruption because it's just this constant wait, wait, wait, wait, wait and the system is going to be very, very slow when that's happening. So, but that was the overview of getting FreeNAS 11 set up and getting your first share set up on there. And that's the bigger goal here. And kind of giving an idea of the ZFS file system and how it works along with the snapshot ability of the file system. Like I said, that's a huge, great feature of it being able to do the snapshots. And I'll probably use some more videos coming along. I said, I'm going to build a specific, I got to physically have parts laying around on the other room so I can build one just so I can test the VM and the hypervisors. I want to get into playing with that. I really liked the idea of building that and putting all those snapshot abilities on there built into FreeNAS, so I think that's pretty cool. So, if you like the content in here, like and subscribe. Hopefully, I got it all right here on FreeNAS and FreeNAS 11. I may have missed a couple of things, but I'll be doing some more videos and more follow-ups on FreeNAS 11. Thanks for watching. Appreciate it.