hey guys, this is my new three-node Proxmox cluster set up with high availability, and in this video, we're going to talk about how I got it set up. So if these boards look familiar, they probably should if you've watched this channel before. Those are Zima board 832s that were provided to me by Zima board months ago. I was going to make this video a long time ago and just never got around to it. So sorry to the folks at Zima Ford for taking so long to do this, but thanks for providing the hardware. I do appreciate that. So these are 832s. These that means it's got eight gigs of RAM and 32 gigs of storage. I do have a one terabyte SSD plugged into each one of them. There's some cables in the back where you can kind of see that plugged in, and then I've got a 64 gig USB drive as the boot. But with all of that said, let's jump over and take a look at

the process of getting this set up uh so that we can then kind of go into with the next video in this little project might be. This video is sponsored by Tuxedo Computers in The Tuxedo Aura 15 gen 2. The Aura 15 Gen 2 comes with an AMD Ryzen 7 5700U that gives you 8 cores and 16 threads while only sipping 15 watts of power. This means the 49 watt-hour battery will get you hours of productivity while on the go. You'll also get the AMD Radeon RX and Vega 8 featuring 8 GPU cores that clock up to 1900 megahertz. The Aura 15 Gen 2 supports up to 64 gigs of dual-channel DDR4 RAM. That way, you can have as many Chrome tabs open as you need for your productivity. With a thickness of less than two centimeters and only weighing in at 1.65 kilograms, taking the Aura 15 Gen 2 will be a breeze. You'll get a 15.6

inch 1080p screen that covers 95 percent of the srgb color space, with a peak brightness of 300 nits. The aura 15 Gen 2 comes loaded with IO ports, including USB 3.2 Gen 2 type c, full feature DisplayPort 1.4, a USB 3.2 gen 1 type a, two USB 2.0 no type A ports, and an HDMI 1.4 Port that includes hdcp. 4K UHD at 30 Hertz native also get a gigabit Lan port and a two-in-one headphone microphone Jack, as well as a Micro SD card slot. For more information or to configure your own Aura 15 Gen 2, check out the link in the description. [Music] your Hardware sorted, of course, the next thing you want to do is get proxmox installed on each of your individual nodes. So of course, you'll need to create a bootable USB using whatever means that you like to use to create your bootable USBS, and you need to boot from that.

bootable USB and start the installation process. Like we've done in previous videos, of course, the first step will be to set up an email address and a password for your root account. Next, you'll give each of your different nodes a host name, an IP address, a Gateway, and a DNS server so that it can communicate with the internet for updates, downloads, things like that. And then, at that point, the installation process will proceed. And then, after several minutes depending on your hardware setup, you'll be brought to a login prompt. On that screen, you'll see the IP address and Port that you'll need to go to in your browser so that you can log into your Proxbox server for the first time. And of course, you're going to do that for each of your individual nodes. So if you've got three, you're gonna do it three times. You've got five, five times, whatever, right? So you're going to do this for each of the individual nodes that you're going to put on your cluster. Okay, so once you've got Proxmox installed on all three of

your nodes. What you'll want to do is get logged into each one of them in separate tabs and then jump over to node number one. So here we are on node number one, and we're on data center. That's where we want to start. Then what we want to do is come over here to where it says cluster, click on create cluster, and then we're going to give it a cluster name. So I'm just going to be original, call it DB cluster. Like so, you've got the option to add additional Network ports here, network connections if you will. Basically, the lower the number, the more priority it will have, and then any additional network connections that you have there will be for failover in case something goes wrong, more bandwidth is needed, or something to that effect. So once we've got our cluster named and we've got our Network, our cluster network setup here, what we can do is click on create. We're gonna go ahead and give this just a second here, and it says task. Okay, so we're going to go ahead and close that.

right there and then, we're going to click here, right on that cluster, and click on join information. Here we've got an IP address, a fingerprint, and some Joint Information. What we want to do is click on copy information, and then we want to jump over to node two. So, we're going to come over here again, we're going to go to Data Center, we're going to go to Cluster, then we're going to click on join cluster and paste that in there. It automatically fills everything out, except for the root password of the first node. So, we want to go ahead and put that in now, like so, and then click on join DB cluster. So now, it says it's stopping the PVE cluster. At this point, this node has become kind of unresponsive, and that's fine, that's perfectly normal. What we can do though is jump over to, over back over to our first node, and here we can see that node 2 is joining. It's got a little question mark right there, and here in a moment, once it has done its

thing that will turn into a check mark like it's done there. And now we've joined the second node to the first node in our DB cluster. So let's jump over and do the same thing on the third node. So we'll jump over to here. We're going to click on through cluster join, paste, put in the root password again. That is the root password of the first node, not necessarily the root password of this node. Hopefully you're using different root passwords on all of your systems, but it's the root password for the first node, whichever one started the cluster. So once we've got that again, we're going to go ahead and click on join the cluster. Again, it's doing the stopping the PVE cluster service. We jump back over to here. Now we can see cluster or DB cluster is 03 set up and ready to setting up there. And we'll be ready to go here in just a moment. So here we are just a moment later, and we can see that all three of the nodes are part of the

cluster now and we can actually administer each one of these nodes from each of the different dashboards. So if we jump over here on DB cluster one or if we come over here to DB cluster, uh, two just like that. And here again, we've got a cluster or DB cluster one and DB cluster two. And again, DB cluster three. We may have to log back in there and that's fine. So basically my point is you could administer all three nodes from any of the three nodes. And I kind of dig that kind of flexibility in a setup like this. So there we go, cluster one, cluster two, cluster three, all three of them again access to all three of the nodes on the cluster. So now that we have our clusters set up, we want to set up storage for each of the three nodes so we can have high availability and replication. So let's jump back over to node one and get and start getting our storage set up. So here we are back on node number one. While we're here though, just real quick, we can kind of take a look at this.

dashboard and see that our status is good. We've got three nodes online, zero offline. Below that, we've got the combined resources of all of the nodes in our clusters. We've got 12 CPU cores, that's four cores per node. We've got about 23 ish gigs of RAM available, of course, that's eight gigs per node. And then for storage, we've got 121 Gigs available, but that's because we haven't actually configured all of our storage. That's just the storage that's available based on our boot drives at this point. And on the right side, we can see the individual nodes. And below that, we can see our guest services or whatever you want to call it, where we're going to have containers and virtual machines. It'll show us what's up, what's down, that sort of thing. So now let's jump over to our first node. Here, we're going to come down to where it says disks. And right here, we can see we've got two separate disks.

have a Dev SDA and Dev sdb. The sdb is the USB drive that we're booting from that's got our operating system, and the SDA is the one terabyte SSD that we're going to use for our storage. Now, if this says usage yes, GPT yes, you may have to go in and wipe the drive in order to use it here. Um, but mine is a fresh drive, so we're good to go. So what I can do is just come down here and click on ZFS, click on create ZFS. We're going to give this a name. We need to make sure that whatever name we give this particular storage pool, the ZFS, do we give it the exact same name on all three nodes so that when containers and VMS are moved from one node to another, their storage is the same. The name of the storage is the same so that they can identify where they need to be at any given time. So we're just going to call this storage. I've got, and the reason I'm deliberately

naming the storage is because um I plan on making another video where I'm going to take an existing proxmox server that's got multiple containers on it and moving all of those containers over to this three node cluster so if you're interested in that let me know in the comment section hit the Thumbs Up Button uh don't forget to subscribe if you haven't already but basically now we've got our storage name here. I'm only using one disk per node. However, if you had multiple disks, you could set up raid this way. Again, I'm just going to use the single disk set up here. I want to make sure that ad storage is checked in this little box right there, but only on the first node. When we get into nodes two and three or further than that if we wanted to go that far, we're only going to have the ad storage check on the first no. That's very important. So we're gonna come down here, we're going to check, we're gonna check the box next

to all of the different storage devices that we want to use again. I've just got the one, so I'm going to click create. We're gonna give this just a second to do its thing. Here we go. Now we've got storage set up. And right here again, we've got that question mark, meaning that it is currently setting up in the background. So while it's doing that, we can jump over to node two and do almost the exact same thing. So we're going to come over to node two. We're going to go to again. We're going to check our disk, make sure that it is available. Right here again, we've got SDA and SDB. We're only interested in SDA. Here again, this one's clean, it's ready to go. So we can come down and click on ZFS. Next, we're going to click create ZFS. Again, we're going to call this storage. Again, single disk, that's what I'm using here. I am going to uncheck that add storage like I mentioned just a moment ago.

going to check the box for the device that I want to use for this storage. We'll click create, and then once that is done, we're going to go over to node number three, do the exact same thing. This looks good. ZFS create ZFS storage single desk, add storage is off. SDA is on, and click create. So at this point, we've got Proxmox installed on all of our nodes. We've created a cluster, and we've joined all of our nodes to that cluster, and we've got our storage setup for each of the different nodes. So the next thing we want to do to get replication and high availability setup is actually create a virtual machine or a container. I'm going to do a container, but we need to do that next. So we move on to the actual replication and high availability section here. So what I'm going to do is I'm just going to come over here to my first node. I'm going to go to Shell. I'm going to do a pveam update. We'll do

pveam available. And then we're just gonna go find one of these that we're going to use later. I always like to download a Debian 11 standard like so. We're going to copy that, and then we'll scroll back down. So now what we're going to do is type in PV eam just like we did before. We're going to say download local because we want to use the local storage that's on the actual device. And then we're going to put in the name of whichever container that we just download or that we want to download rather. So we're going to go ahead and just paste that in like so. And I'm just going to hit enter. We're gonna give this a second to download and save where it needs to save. There we go. Now we have a container available that we can deploy. So let's go ahead and do that. Now what we're going to do is come up to the top right, click on create container. The node will be on cluster number one. We're going to

course change that right here if we want to, but I'm just going to put it on one. The container ID is fine. We're going to call this, uh, first demo just for the host name. It doesn't really matter. Of course, this is just for demonstrative purposes here, but now I want to give it a root password. And once we've entered that twice, we can move on to the next step and click on template. We can select the template we just downloaded. We can go to disks, and for this, we can go. We're just going to select storage because that's the storage pool that we just created. We want to select a disk size. Eight gigs is probably fine. It depends on what you're doing, but I'm going to call it 16 just because. For our CPU, we're going to give it, uh, we're gonna give it one core. For memory, I'm going to give it 512 Megs. Mags, but I'm going to give it a gig of swap just so I can type in something here for our Network.

going to come over to here. I'm going to make this DHCP for right now. For DNS, I'm going to put in some DNS like so, that way we've got DNS that isn't confined to our local network. And then I'm going to click confirm, and I'm going to say start after created. And then I'll click finish. So once this container is up and running, then we can move on to replication and high availability. Okay, so here we've got our task. Okay, that means we're good to go. So I'm going to go ahead and close this. And then right here, we can see first demo is up and running. Just for the sake of it, let's do one more, just so we've got some more stuff to play with. Here, a few moments later. Okay, so at this point, we can see that we have two different containers up and running in node one. So now let's go ahead and get replication configured. So what we're going to do is click on our first container here. And then what we'll do is come over to replication.

we're going to click add, and then we're going to Target one of the other nodes. At this point, it doesn't really matter which one you Target because we're going to Target all of them through multiple steps here. But basically, we're saying, Hey, container number 100, we're going to Target cluster node number two. And by default, it's just going to do this every 15 minutes, kind of synchronize the nodes to make sure that everything is current and up to date. You can rate limit this if you want to. You can leave a comment and have it enabled. Once you're happy with this, click create. And then we're going to do this one more time, like I mentioned. This time, though, we're going to go over to Cluster number three, and we're going to leave all of this the same and click on create. Then we can come up, we can click our first option here, our first Target, and click on schedule now. And then we can click our second Target and click schedule now. And here, I'm on the right, where it says

next sync is pending. We're going to give this amended to do its thing, and then it will let us know when it's done and ready to go. Okay, so both of these now say status okay. Uh, how long it took to do it when its next sync is and how often it's scheduled again 15 minutes. So now we've got our first container done. Now we need to move over and do the second container that we've got here, that's number 101. So we're going to follow the same steps. We're going to click our container or our virtual machine, whichever you happen to be running. We'll click add again. We're going to do DB cluster 2. We're going to leave everything else here the same because it's fairly standard good stuff. We'll click create, and then we'll do the same thing here, and we're going to come down here and do cluster number three create, and then again we can schedule now on both of those. And over here again it says pending. We're going to go ahead and give

that just a minute to do its thing, and then once this is done, we can move on to high availability. Okay, so now both of these have a status of okay. We can say when the next thing is how long it was, and again how often it's scheduled. Now, if we want to make sure that that's actually worked, what we can do is come over here to our storage on all of these nodes really, and we can see a sub volume, uh, 100 disk zero, so volume 101 disk zero. If we come over to Cluster number two, again, same thing, cluster number three, same thing, that tells us that our synchronization, our replication has worked. So now we can actually move into the high availability part of this. So to do that, what we're going to do is come over to Data Center, we're going to click on h a right here, and then what we want to do up at the top, it says Quorum. Okay, that means that where everybody's happy with how things are progressing, all of the nodes are working.

together. So what we want to do is add some resources, and what I mean by resources, or rather what they mean by resources, are the virtual machines and containers that we want to monitor for high availability. So what we'll do is click on ADD. We're going to click on the first demo here. All of this stuff in here you can just leave as it is, and we'll click add. We'll do the same thing oops right here, and we'll do second demo and click add. And now that we've got our two resources or containers VMS, those are pretty synonymous right now. Up at the top, we can still see our Quorum is okay, but now that we can see DB cluster01 is our Master, but all three nodes are currently active. Okay, so now at this point, we should be good to go, but let's make sure that we are actually good to go by shutting down our first node. Now, before we do that, what I want to do is come over here to our first, our first demo container here. I actually want to go to console.

we're going to log in and I want to get the IP address of that note or that container. That container, and it's going to be 192.168.0.40. So what I'm going to do is I'm going to do a ping oops 192.168.0.40. I want to make sure that it gives me an IPv4 address. That's what the dash 4 is for, and then Dash T will just keep it going until I tell it to stop. So I'm going to go ahead and do that. And then what I'm going to do is come over here to my Armada controller. We can see that we've got a time of less than one millisecond here. So I'm going to come over to my Armada controller. And right here, I can see prop proxbox node three two and one. What I want to do is actually shut off node one. So what I'm going to do is come over here to devices. I'm going to go to my 24 Port switch. I'm

going to click on ports. I'm going to come over to uh over here. Oops, that's too far, and cluster number one is on Port 16. So what I want to do is check or click that box. Profile is going to be disabled, and I'm going to click apply. Then I can come over. Let's go to node two because node one is going to become non-responsive. So let's open this back up, and all of a sudden our request has timed out. So at this point we can just kind of hang out and wait. What I want to do though is uh toggle both of these open and bring this back over so that we can kind of see in real time. I'm going to speed ramp this, but we can see in real time how these uh containers move from node one to possibly node 2 or node two and three or just three. We'll let the system decide what it wants to do here, okay? So here we are just a couple of minutes later. That does take a little bit of time, and of course, the more nodes

you have the longer it may take depending on your network throughput and what kind of a connection you've got. Those sorts of things. You could actually reduce the amount of time, the amount of downtime, uh, when it, when there's an outage like this. If you had a ceph server set up, uh, that was kind of a shared storage solution between the three, rather than having individual storage nodes or storage pools on each one that are somewhat shared and synchronized but but a a ceph solution would actually be a better way to have a smaller amount of downtime in the case of a node going down. So here you can see that it actually did separate them out by going to uh the first demo went to Cluster number two and or the node it says cluster here. I really should have named it something else but uh but then a second demo went to uh node number three and of course I can come right back over to here and I can turn that Port back on like so. Now ultimately that doesn't do anything for us other than just turn the

the network Port back on uh it's not going to automatically move those containers or VMs back over to that original node uh it's just now that node is available for if uh more resources are needed by those nodes or another node goes down now that node is back and available uh for use in that cluster again so there you go there's how to set up a basic high availability Proxmox cluster using three nodes uh hopefully you found the video helpful if you did do me a favor give the video a thumbs up maybe consider subscribing if you haven't already um also I've been putting this out in my videos here lately if you're interested in supporting the channel and getting something in return which means uh videos with no ads that's no baked-in ads that's no YouTube ads just just straight to the content uh you can join my patreon my DV Tech dot fans website or become a member here on YouTube however if you join on patreon or DB tech fans you can get ad-free content for just one dollar a month if you want

to go that route so but with that said, I do want to go ahead and wrap this up. I want to thank you for spending a few minutes of your day with me today, and I will talk to you in the next video.

Setting Up My First Proxmox High Availability Cluster

Setting Up My First Proxmox High Availability Cluster