Hi
We have now been running Proxmox VE for a while and even before Proxmox Backup Server was released.
After switching to Proxmox Backup Server we have noticed that during the time where the backup of a VM is running, the Disk IO graph spikes to somewhere between 2G and 5G, which means that if we want to see disk IO for fx. the past day in the Proxmox VE GUI we cannot really see the actual load.
Is there a way to avoid these spikes to show in the stats.
We have not observed this using the "old" vzdump method that was standard until PBS was released.
We have observed this across different environments where either PVE managed Ceph 16 (and 17) are used as well as single-node ZFS deployments. In all cases the PVE OS disks are separate from any storage used by the virtual machines
output of pveversion -v on PVE node:
Proxmox Backup Server is version 2.3.3
We have now been running Proxmox VE for a while and even before Proxmox Backup Server was released.
After switching to Proxmox Backup Server we have noticed that during the time where the backup of a VM is running, the Disk IO graph spikes to somewhere between 2G and 5G, which means that if we want to see disk IO for fx. the past day in the Proxmox VE GUI we cannot really see the actual load.
Is there a way to avoid these spikes to show in the stats.
We have not observed this using the "old" vzdump method that was standard until PBS was released.
We have observed this across different environments where either PVE managed Ceph 16 (and 17) are used as well as single-node ZFS deployments. In all cases the PVE OS disks are separate from any storage used by the virtual machines
output of pveversion -v on PVE node:
Code:
proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve)
pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4)
pve-kernel-5.15: 7.3-1
pve-kernel-helper: 7.3-1
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph: 16.2.9-pve1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-2
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.7-pve1Proxmox Backup Server is version 2.3.3