Thank you I have not seen it.
But please note again that batman is:
- full mesh (rtsp is "only" tree based) so
- fault tolerant with fast recovery (as rtsp)
The only missing feature in batman is mtu 9000.
After reading this thread
I should suggest to do the opposite: NEVER limit the bandwidth and put ssd disks on backup server!
First I want to thank you. It is years that I have several vm slowness problems during backup. I have read many many many threads of people with same problems and we lost many days to understand where the problem is and now you finally showed it to me.
I supposed that backup was done in the...
Ok I have checked and I see that unfortunately mtu is locked to 1500.
So I have tried vxlan but I have discovered a big problem: vxlan is not fault tolerant!
Batman does a full mesh, so if I detach a cable between two servers batman routes (at level 2) packets to other path and so all three...
I need that:
And I suppose many people need this. If you want to monitor several proxmox installations using zabbix or nagios and you want a graph of backup duration and a trigger failed/ok.
Sorry I meant: can YOU officially backport new features of pvesh in old proxmoxs?
I am interested too in this thread. I have written also in this thread: https://forum.proxmox.com/posts/433931/
In the backup email that proxmox sends even in "old" versions (5, 6...) there are all informations you need to put in a monitoring solution like zabbix or nagios.
I have almost the same problem:
- monitoring backups in pve;
- monitoring backups made with pbs;
- monitoring pbs;
I have tried several solutions (started with pve metric server) but the only pratical way is to build a custom script and to add it to zabbix.
The problem is that I must be...
After many reboots I have been able to reenable migration and shutdown. One of the servers was still on 5.11 perhaps it was the problem.
Anyway there is a general problem of slugginesh.
Please note that I use virtio-scsi on all VMs, linux and windows.
I am playing with io_uring and so on but...
the setup is just like in the link @vesalius has indicated.
My /etc/network/interfaces (omitted boring part) is:
iface eno1 inet manual
iface eno2 inet manual
iface eno3 inet manual
iface eno4 inet...
Yes infact actually I have configured it manually.
Yes I will check which commands I have done last year
Did not know about it, two questions:
- is it production stable?
- is it complex to setup?
Batman is more than 10 years old so it is stable, battle tested and very easy to setup.
Batman is an established protocol for mesh networks: batman
The advantages are:
- level 2 easy configuration (no need to use level 3)
- the source node talks directly to destination node ( no bandwidth wasted)
- very fast convergence time if a link is down