It depends A cluster only really works with shared storage In that case, the hard drive doesn't move when a VM is migrated as part of HA, although the contents of the RAM will need to be if the VM is live If a node fails, another node will reset the VM to take over the file lock(s) and there will be a loss of data if it was in RAM and wasn't written to disk I don't know the specifics of KVM for local storage transfers But one of the options I've noticed for migrating is to keep the original disk, so I assume the process is similar At a high level hypervisors copy the data from the existing hard drive to the new destination and then they start to keep the two drives in synch They do the same for the RAM if it's live Back when I was studying VMware for instance, it would keep the two VMs in sync and then there would be a brief pause and the old VM would be disconnected and the new VM would take over on the new node After that the older files would be deleted
It's off topic to the video. I am building my promox server, I am using right now 1 pi and a Dell PC whit docker both in one network segment, a pi running home assistant whit diferente network segment my IoT network. The idea is to have everything on proxmox. My question is, do I need to add a nic to have the separation of my network? Thank you. I am following your videos for when I build it. Thanks
Yes you do need different interfaces to separate networks They don't need to be physical though You can create logical interfaces, if the operating system supports it, but you can miss out on bandwidth because it will be shared Check out my video for Proxmox and VLANs on a single NIC for instance czcams.com/video/ljq6wlzn4qo/video.html
It looks great but I think proxmox does not support fail-over IP, so when you move VM still the IP allocated to the first node, I think VM will not be reachable?
The VM will keep it's IP address if it was assigned statically If it was assigned by DHCP, it will be retained most of the time It's usually desktop hypervisors that provide their own DHCP service to their VMs but they wouldn't be clustered like this to provide HA An enterprise hypervisor like PVE relies on a separate DHCP server to allocate IPs to VMs The risk to using DHCP is if the IP address expired and was allocated to another computer while the VM was offline. Highly unlikely but possible On some hypervisors the MAC address can change when a VM is migrated like this, which can then be a problem for reserved IPs in DHCP But with PVE I noticed the VM keeps the same MAC address So as long as the IP address is static or reserved there shouldn't be a problem
If you want to learn more about Proxmox VE, this series will help you out
czcams.com/video/sHWYUt0V-c8/video.html
The best proxmox HA Guide!!! thank you!
Thanks and good to know the video was helpful
Really insightful thank you.
Good to know the video was helpful
Thanks for the feedback
Another Great video David Awesome content thank you again for your insight.
Glad you liked it
great info, thank you good sir
Good to know the video was helpful, so thanks for the feedback
it will automatically create new disk of VM on node 2? how it keep the disk data of VM on node 1 and migrate to node 2?
It depends
A cluster only really works with shared storage
In that case, the hard drive doesn't move when a VM is migrated as part of HA, although the contents of the RAM will need to be if the VM is live
If a node fails, another node will reset the VM to take over the file lock(s) and there will be a loss of data if it was in RAM and wasn't written to disk
I don't know the specifics of KVM for local storage transfers
But one of the options I've noticed for migrating is to keep the original disk, so I assume the process is similar
At a high level hypervisors copy the data from the existing hard drive to the new destination and then they start to keep the two drives in synch
They do the same for the RAM if it's live
Back when I was studying VMware for instance, it would keep the two VMs in sync and then there would be a brief pause and the old VM would be disconnected and the new VM would take over on the new node
After that the older files would be deleted
It's off topic to the video. I am building my promox server, I am using right now 1 pi and a Dell PC whit docker both in one network segment, a pi running home assistant whit diferente network segment my IoT network. The idea is to have everything on proxmox. My question is, do I need to add a nic to have the separation of my network? Thank you. I am following your videos for when I build it. Thanks
Yes you do need different interfaces to separate networks
They don't need to be physical though
You can create logical interfaces, if the operating system supports it, but you can miss out on bandwidth because it will be shared
Check out my video for Proxmox and VLANs on a single NIC for instance
czcams.com/video/ljq6wlzn4qo/video.html
@@TechTutorialsDavidMcKone thank you
It looks great but I think proxmox does not support fail-over IP, so when you move VM still the IP allocated to the first node, I think VM will not be reachable?
The VM will keep it's IP address if it was assigned statically
If it was assigned by DHCP, it will be retained most of the time
It's usually desktop hypervisors that provide their own DHCP service to their VMs but they wouldn't be clustered like this to provide HA
An enterprise hypervisor like PVE relies on a separate DHCP server to allocate IPs to VMs
The risk to using DHCP is if the IP address expired and was allocated to another computer while the VM was offline. Highly unlikely but possible
On some hypervisors the MAC address can change when a VM is migrated like this, which can then be a problem for reserved IPs in DHCP
But with PVE I noticed the VM keeps the same MAC address
So as long as the IP address is static or reserved there shouldn't be a problem
@@TechTutorialsDavidMcKone Yes that would be correct. Long as MAC address remains the same you're good to go.