Recent content by _gabriel

As VM has its own public ip, they are not connected to PVE network. Allow PVE WAN IP in each VM firewall.

it's not Proxmox related, it's a tcp/ip basis. I've no use case for "sport" neither experience to write an example.

remove "sport" as you often don't control the source port.

Awesome !

edited on PVE side isn't ? what about 128 concurrency and 16 threads ?

Have you tried tuning above ? CONCURRENCY & THREADS envs ?

Monitor within guest as the schedule time (temporary change schedule time)

Network graph displays MB/s instead Mb/s https://forum.proxmox.com/threads/units-of-measure-on-network-traffic-graph.170161/

What backup mode for scheduled task ? Snapshot / Suspend / Stop ?

For the Restore process, you can tune settings : https://forum.proxmox.com/threads/abysmally-slow-restore-from-backup.133602/post-784918

PVE version, as restore is PVE side. PVE 8.4 require updates to allow "Restoring from Proxmox Backup Server now fetches multiple chunks concurrently in each worker thread. This can improve the restore performance in setups with fast network connections and disks. The number of concurrently...

What PVE version ?

it's expected as it's same OS "binaries", Windows build 26100

-hypervisor implies perfs penalty , use it as a last resort.

After you discover how it works under the hood, you will follow the recommended way : Local PBS then WAN PBS Remote Sync from. Give a try , I bet on no more QEMU guest agent stopped with a local PBS.