Last edited:
How is this network segmented? Is this a segmentation using dedicated hardware or software defined segmentation using e.g. vlans?I have a separate network segment for my Proxmox Backup Server within my Proxmox cluster
The Migration network has nothing to do with the network used for backups to PBS. But sure, if your cluster network is not on a dedicated (physical) network, than any traffic going over the same network interface might increase the latency, and since corosync requires low latency the cluster might be affected.If I change the Migration Settings in the Datacenter from "Default" to "MyPBS Segment," could this impact the cluster's health in any way?
Yes, this will have effect without a reboot, i assume your network configuration is already in place?Additionally, would I need to restart the nodes for this change to take effect, or will it apply without a reboot, allowing the next VM/Container synchronization to use this network segment?
The change in migration network will not change the network used for corosync.Also if this is to happen i suppose the corosync traffic would still go trough the Management network?
I have separate 10G NIC on every node and my PBS and they are in separate network and connected on different network switch than the Management interfaces. So i suppose switching to this segment for the migrations should be ok. Thank you for your answer !How is this network segmented? Is this a segmentation using dedicated hardware or software defined segmentation using e.g. vlans?
We use essential cookies to make this site work, and optional cookies to enhance your experience.