Setting Up My First Proxmox High Availability Cluster

preview_player
Показать описание
This video is sponsored by Tuxedo Computers and the Aura 15 Gen 2.

/=========================================/

In this video I'll show how I set up my new 3 node Proxmox High Availability Cluster.

Thanks to @ZimaBoardOfficialChannel for providing the devices that made this video and this setup possible!!

Here is the hardware I used:

/=========================================/

Timestamps:
0:00 Intro
0:52 Sponsor
3:30 Creating a Cluster
6:45 Configuring Storage
10:31 Deploying a Container for Replication & High Availability
13:30 Configuring Replication
15:45 Configuring High Availability
16:37 Verifying Operation

Proxmox Playlist:

/=========================================/

Get early, ad-free access to new content by becoming a channel member, a Patron or signing up for the members' only website!

/=========================================/

The hardware in my recording studio is:
✔ Custom PC w/ Ryzen 2600, 32GB RAM, RTX 2070, Assorted Storage

/=========================================/

The hardware in my current home servers:

/=========================================/

✨Find all my social accounts here:

✨Ways to support DB Tech:

✨Come chat in Discord:

✨Join this channel to get access to perks:

✨Hardware (Affiliate Links):
Рекомендации по теме
Комментарии
Автор

Honestly proxmox makes it so easy! Only problem I ran into was using just two nodes. Ended up giving my main node two votes and everything worked fine. Getting a pi 5 to use as the third node.

dominick
Автор

👍This is the best video of the year on all of YouTube. Cannot thank you enough!

chromerims
Автор

Hi. Nice video.
Seems that after 8:57 where you create the storage for each node (with the same name as you ve mentioned) you ve forgot to show something,
else I can t explain the different behavior in my cluster.
What I mean by that is, if you keep checked the box <<Add Storage>> on the first node only and not the others, then whichever node you re on gui you ll see only the Storage of the first node. All the others will be like they have no storage (even from each node's gui, it can t be seen).
The same goes if you go individually to node 2 or 3 and try to create a VM. At the tab where you need to choose storage space for the VM you can only choose local. No Storage. So something you missed to show I guess.

PS By the way you didn t check thin provision option for the Storage at

New edit: The only way for the storage to be seen to other nodes too is go to and inside that window list down at option Nodes all 3 nodes and check them. Then automatically that storage is visible to all other nodes too. Even though, what would be the purpose for all 3 nodes to see only the first one's storage and not theirs. In case of first node failure his Storage (which the other two see) would be absent so where is the HA and replication to this scenario?

dimitristsoutsouras
Автор

Nice video! If you haven't already setup Proxmox Backup Server, do so! It's amazing. Does the obvious thing of backing up VMs, and containiners but also does dedup, replication to another backup server and tape support. But I also like that it supports backing up bare metal Linux PCs too.

donaldwilliams
Автор

Thanks for the demo and info, have a great day

chrisumali
Автор

Great explanation - been running 3 nodes on ceph but am planning to move over to zfs. Thanks

CJ-vgtg
Автор

This is really interesting and you made me wanna buy more hardware just to play this 😂

ahyi
Автор

Excellent tutorials and walkthrough! thank you for sharing.... I watched several of your videos and do have a questions. I see you talked during the wrap up about CEPH and watch your other videos and also see you move away from CEPH due to the overhead (similar to your reason for leaving OMV and moving to ProxMox). Have your found a sweet-spot on storage implementation for proxmox? balanced resource usage and failover time in HA?

thank you again!!!

JuanCintron
Автор

Great video, proxmox is a really nice setup for a homelab.
I like the lightweight containers, but I also run kubernetes and traeffic

martinbower
Автор

Great video again David, i love proxmox!

drbyte
Автор

Great video, thanks! It seems I cannot replicate unless I have ZFS on both ends... But still very usable, thanks!

rklauco
Автор

Thank you so much for this video :) Lots of help. Subscribed!

brainamess
Автор

Hi, great video...
just a suggestion: in a set like yours I will try definetively with a true network storage system like gluster.
Is not ceph but works very well with proxmox and with HA. The migration from a host to another is blazing fast and recover VM from a failed node faster than a replica solution like this.
It's a viable solution between ceph that require nore resources and little cluster like this.
In you case you can allocate the second ethernet to handle gluster.

posalab
Автор

Great Video Loved It. Thanks for the inspiration.

HSVEOCT
Автор

Do you know if this works via remote VPN or tunnel? I know it would be slower but would it work? I have 3 locations with internet. Was thinking of Tailscale tunnel on all three but have them in cluster and use HA?

WhiskeyBackRoads
Автор

Nice clip, thank you! a question: must the cluster nodes have the same hardware configuration or can I have servers with different cpus, quantity of RAM?

PaoloLaitempergher
Автор

Hi David, any idea why it throws the error "no replicatable volumes found (500)" when trying to add a VM to replication? I'm using NFS storage in my cluster if it helps. Thanks

kklip
Автор

Thx for the video!
Can I achieve what you describe here regarding Storage on zfs with only one disk? TIA

yuriw
Автор

please do this demo again but with the ceph storage !!!

fbifido
Автор

thank you so much for this video, it really helped me out setting up a three node cluster. I have one question though: let’s say that the first (master) node goes down and the lxc/vm’s move to the other nodes. you mentioned that after the first node comes back online the lxc/vm does not automatically move back, but continue to run on node 2 or 3. but how does replication work from that point on? asking as we set-up the replication from node 1 > node 2 and node 1 > node 3… if we continue to add data to the lxc will that only be available on the current node or should we set up replication for example from node 2 > node 1 / node 3? thanks so much for a great tutorial again and have a great weekend!

agalbulescu