You know what I love about your videos? You get straight to the point with little to no bullshit along the way. So many times I have found tutorials online where the creator will talk about his life story before getting to the first step. Not you, sir. You get straight to the point so that everyone's time is not wasted. I really appreciate you and your expertise. I have to find your Patreon or whatever you use to take donations.
Just wow man! Thank you so much for those kind words 🙏 I'm so glad my video help you and I try my best to get to the point lol. Thanks, Glad to Help! www.patreon.com/GreyTech
It should be noted that if you create a cluster with only two nodes, if a single node goes down you will NOT be able to access your panel at all. Because of how the quorum system works, if half your nodes are down, the entire cluster stops working and goes read-only. For small home setups you probably DON'T want to cluster your nodes. Just keep multiple bookmarks in your browser.
I think its manageable as long as i make sure to frequently backup stuff and just be prepared that if one of the two stops working i would need to start from scratch
‼️All these should come with a HUGE warning ⚠️ that explains that reverting it back and separating the cluster OFTEN goes wrong and is not a simple process. ⛔️
Can you explain the issues one would face while disconnecting the clusters? I was planning to setup a second proxmox node to get it to join to my prinary, but now want to be cautious
@@rajivvishwa proxmox is not designed to de-cluster. I did it and was doing some testing and can’t recall why exactly had to remove the second machine from the cluster and found out that you have to manually change a lot of code in proxmox and force remove the other machine from the list because it will still show and a lot of other issues because even when you try to clean it all up there’s remaining code in the main one that cant be easily fixed at the end had to reformat the main server and re-install. Luckily I am running a Proxmox backup server as well and was able to restore all the vm machines and online services I am running like a ecommerce website etc. Proxmox Backup Server is the most important thing you can add to your proxmox server hands down!
@@rajivvishwa renaming the host is no longer possible using the standard method of renaming /etc/hostname Deleting the old cluster is easy, but I sometimes run into issues where is still thinks it’s in a cluster. Lot of the config and management is now saved in /etc/pve/cluster And if you delete that, thinking it will reset the cluster config, you’re in for a hassle
@@gailsiebenaler7976 No, I ended up moving away from Proxmox and started using CasaOS. It doesn't give me HA, but I'm a home user. I really don't need HA at the moment. However, I think I will install Proxmox on a different x86 mini PC and do some different things with LXC. Proxmox is starting to be like that girlfriend you just can't say no to. No matter how many times we break up I keep coming back
no proxmox basically moves the vms between the hosts, but there is no ressource sharing, like computing half on one node and half on the other (as far as I know).
@@dennisdesgehtdichnixan2022 Thank you for pointing that out. I thought it did, but I was wrong. Here is what I figured out. When you set them up in a Proxmox cluster, one of the great things is that you can manage all of them from a single web interface. This centralized management makes it much easier to handle tasks across the entire cluster without having to jump between different machines. Now, when it comes to CPU and memory resources, each node (which is just one of your PCs) uses its own hardware. So the CPUs and RAM aren't pooled together across the nodes. Instead, when you create a virtual machine (VM), you assign it to a specific node. That VM then uses the CPU cores and memory from that particular machine. This means that the performance of a VM depends on the resources of the node it's running on. For storage, things get a bit more flexible. Proxmox supports shared storage solutions like NFS, iSCSI, or Ceph. By setting up shared storage, all the nodes in your cluster can access the same data. This is really useful because it allows you to migrate VMs between nodes without any downtime, which is called live migration. It also enables high availability, so if one node fails, the VMs can automatically restart on another node. Networking is also shared across the cluster. You can set up virtual networks that span all your nodes, so your VMs can communicate with each other as if they were on the same physical network, even though they're running on different machines. Proxmox even supports software-defined networking features if you need more advanced configurations. In reality, while CPU and memory resources are tied to individual nodes in a Proxmox cluster, storage and networking can be shared across all nodes. This setup allows you to take advantage of the combined capabilities of your four PCs while maintaining control over where and how resources are allocated.
Does it matter on which device you create the cluster? I have a performant NUC and a cheap-o mini server. I want to know if the "main" server now needs more cpu/memory to manage the other nodes
I had those .conf on the other server with other machines, so he couldnt move them as there was already those files in the other server... Weird as those are supposedly two different systems with their own files...
Is it possible to have multiple servers run a single VM with Proxmox? Like combining all their computing power into one system? As I see here, Proxmox cluster seems like it just combines the dashboards but the servers are still independent.
Holy Batman, I almost lost 10 nodes! After doing this, you might lose the "local-lvm" storage configuration. Without it, all nodes that use it will break and won't start. Good news: the data isn't deleted, just the configuration is overwritten. To fix it, manually re-add the storage: Go to Datacenter -> Storage -> Add. Select "LVM" (if it was LVM type) and use the same ID, "local-lvm." Defaults should be fine, but make sure it's not shared. If you don't remember the storage name/ID, check the Tasks error log for something like "Error: storage 'local-lvm' does not exist.
Did everything to add a second node to my cluster but now getting - could not activate storage 'local-zfs', zfs error: cannot import 'rpool': no such pool available (500) Any advise?
At the part where you just deleted the .conf files of the Vms by cut-paste them via WinSCP, how come and you are sure the attributes of those files are carried away ? Usual this kind of copy requires special programs or parameters like robocoby. I believe that the attributes didn t passed to the other side (even though practically it seems Vms are working after the transfer again)
Bro, your videos are perfect. Fast, to the point, efficient, and effective. It provides everything I need to recreate what you did in my own environment. Thanks!! 🫡
All good then? The problem start when you want to remove a Node from a Cluster, be very careful how you setup nodes inside clusters, it can be your worst nightmare especially if you work on a Clients Infrastructure, you drop the ball in there you better know a quick exit like setting his Server room on "fire " by "accident" and then make sure the Fire Brigade wets those servers down properly so not a single one lives.
You know what I love about your videos? You get straight to the point with little to no bullshit along the way. So many times I have found tutorials online where the creator will talk about his life story before getting to the first step.
Not you, sir. You get straight to the point so that everyone's time is not wasted. I really appreciate you and your expertise. I have to find your Patreon or whatever you use to take donations.
Just wow man! Thank you so much for those kind words 🙏 I'm so glad my video help you and I try my best to get to the point lol. Thanks, Glad to Help! www.patreon.com/GreyTech
Just awesome 👍
good man, simple instruction. thanks very much and be blessed
It should be noted that if you create a cluster with only two nodes, if a single node goes down you will NOT be able to access your panel at all. Because of how the quorum system works, if half your nodes are down, the entire cluster stops working and goes read-only. For small home setups you probably DON'T want to cluster your nodes. Just keep multiple bookmarks in your browser.
I think its manageable as long as i make sure to frequently backup stuff and just be prepared that if one of the two stops working i would need to start from scratch
doesn’t HA fix this??
I use single nodes with pmbs VM on each one backing up the other
Good stuff, thanks!
Thank you for the awesome feedback 😊
Amazing demonstration. I am creating a cluster of 2 soon
heck ya! very cool! thank you for the feedback
Imagine 20 ....
nice one, helped me a lot. thanks!
cheers dude this is great
Great Video!
Can you do a video for building out the Proxmox HA cluster?
We sure can
Great video. Thank you so much
thank you for the feedback! we appreciate very much!
‼️All these should come with a HUGE warning ⚠️ that explains that reverting it back and separating the cluster OFTEN goes wrong and is not a simple process. ⛔️
Can you explain the issues one would face while disconnecting the clusters? I was planning to setup a second proxmox node to get it to join to my prinary, but now want to be cautious
@@rajivvishwa proxmox is not designed to de-cluster. I did it and was doing some testing and can’t recall why exactly had to remove the second machine from the cluster and found out that you have to manually change a lot of code in proxmox and force remove the other machine from the list because it will still show and a lot of other issues because even when you try to clean it all up there’s remaining code in the main one that cant be easily fixed at the end had to reformat the main server and re-install. Luckily I am running a Proxmox backup server as well and was able to restore all the vm machines and online services I am running like a ecommerce website etc. Proxmox Backup Server is the most important thing you can add to your proxmox server hands down!
@@rajivvishwa renaming the host is no longer possible using the standard method of renaming /etc/hostname
Deleting the old cluster is easy, but I sometimes run into issues where is still thinks it’s in a cluster. Lot of the config and management is now saved in /etc/pve/cluster
And if you delete that, thinking it will reset the cluster config, you’re in for a hassle
So I did this. Is there a way to share resources in the VM in the cluster? Turning my quad CPU in the VM into an octacore CPU?
Did you ever figure this out?
@@gailsiebenaler7976 No, I ended up moving away from Proxmox and started using CasaOS. It doesn't give me HA, but I'm a home user. I really don't need HA at the moment.
However, I think I will install Proxmox on a different x86 mini PC and do some different things with LXC. Proxmox is starting to be like that girlfriend you just can't say no to. No matter how many times we break up I keep coming back
no proxmox basically moves the vms between the hosts, but there is no ressource sharing, like computing half on one node and half on the other (as far as I know).
@@dennisdesgehtdichnixan2022 Thank you for pointing that out. I thought it did, but I was wrong. Here is what I figured out. When you set them up in a Proxmox cluster, one of the great things is that you can manage all of them from a single web interface. This centralized management makes it much easier to handle tasks across the entire cluster without having to jump between different machines.
Now, when it comes to CPU and memory resources, each node (which is just one of your PCs) uses its own hardware. So the CPUs and RAM aren't pooled together across the nodes. Instead, when you create a virtual machine (VM), you assign it to a specific node. That VM then uses the CPU cores and memory from that particular machine. This means that the performance of a VM depends on the resources of the node it's running on.
For storage, things get a bit more flexible. Proxmox supports shared storage solutions like NFS, iSCSI, or Ceph. By setting up shared storage, all the nodes in your cluster can access the same data. This is really useful because it allows you to migrate VMs between nodes without any downtime, which is called live migration. It also enables high availability, so if one node fails, the VMs can automatically restart on another node.
Networking is also shared across the cluster. You can set up virtual networks that span all your nodes, so your VMs can communicate with each other as if they were on the same physical network, even though they're running on different machines. Proxmox even supports software-defined networking features if you need more advanced configurations.
In reality, while CPU and memory resources are tied to individual nodes in a Proxmox cluster, storage and networking can be shared across all nodes. This setup allows you to take advantage of the combined capabilities of your four PCs while maintaining control over where and how resources are allocated.
Thank you!
glad it worked for you!
@@GreyTechLive it did migrate, finally!...but...lol. one of my ct's won't boot. "'101/vm-101-disk-0.raw' contains illegal characters". Oops.
Does it matter on which device you create the cluster? I have a performant NUC and a cheap-o mini server. I want to know if the "main" server now needs more cpu/memory to manage the other nodes
Im trying to copy config files back, and am getting the error that the filesystem is full, is there a fix?
I took out all the .conf files and now I cannot move them back because it says that the File already exists....
Now im screwed...
HELP
I had those .conf on the other server with other machines, so he couldnt move them as there was already those files in the other server...
Weird as those are supposedly two different systems with their own files...
So in this example, clustering allows you to manage the other clusters from a “master” login… but not share resources with each other right?
Does it matter if the spec is different between the clusters or is it better to keep them a similar spec?
I have two proxmox servers. But each has different specs. Do they both need to the same internally to do this ?
Same cpu is think.
@@pascalabessolo5350 oh okay. Thanks for the reply. I just left them be and they operate independently of each other.
Is it possible to have multiple servers run a single VM with Proxmox? Like combining all their computing power into one system? As I see here, Proxmox cluster seems like it just combines the dashboards but the servers are still independent.
thanks
Holy Batman, I almost lost 10 nodes! After doing this, you might lose the "local-lvm" storage configuration. Without it, all nodes that use it will break and won't start.
Good news: the data isn't deleted, just the configuration is overwritten. To fix it, manually re-add the storage:
Go to Datacenter -> Storage -> Add.
Select "LVM" (if it was LVM type) and use the same ID, "local-lvm."
Defaults should be fine, but make sure it's not shared.
If you don't remember the storage name/ID, check the Tasks error log for something like "Error: storage 'local-lvm' does not exist.
Did everything to add a second node to my cluster but now getting - could not activate storage 'local-zfs', zfs error: cannot import 'rpool': no such pool available (500) Any advise?
ruclips.net/video/cQ7_cRaTklI/видео.html
How many nodes could manage in a cluster? it is the same way in proxmox 8.2.4 ?
Yes proxmox I believe can manage around 50 nodes efficiently.
At the part where you just deleted the .conf files of the Vms by cut-paste them via WinSCP, how come and you are sure the attributes of those files are carried away ? Usual this kind of copy requires special programs or parameters like robocoby. I believe that the attributes didn t passed to the other side (even though practically it seems Vms are working after the transfer again)
can i connect/manage a pimox cluster from a standard x86 proxmox datacenter interface?
Bro, your videos are perfect. Fast, to the point, efficient, and effective. It provides everything I need to recreate what you did in my own environment. Thanks!! 🫡
Dude sweet! Thanks man appreciate the good feedback 👍
I second that. One sentence intro, then straight into the good stuff.
All good then? The problem start when you want to remove a Node from a Cluster, be very careful how you setup nodes inside clusters, it can be your worst nightmare especially if you work on a Clients Infrastructure, you drop the ball in there you better know a quick exit like setting his Server room on "fire " by "accident" and then make sure the Fire Brigade wets those servers down properly so not a single one lives.
i dont even have that option to create a cluster wtf
How to create 2 clusters on the same proxmox server. So, 1 server with 2 clusters
You really need a script before video recording
Nope
Brother is it possible to make cluster between two vps,
Vps are in two different regions
up