Recent content by f.cuseo

  1. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    But... same node, different vm: INFO: 100% (64.0 GiB of 64.0 GiB) in 5m 40s, read: 508.0 MiB/s, write: 4.0 MiB/s INFO: backup is sparse: 56.17 GiB (87%) total zero data
  2. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    No changes, except for restore that now works; this is the same vm very slow in backup: progress 100% (read 64424509440 bytes, zeroes = 13% (8841592832 bytes), duration 218 sec) So, slow backup, fast restore (fast only with 6.14 kernel both on PVE 9.1.1 and PBS 4.1).
  3. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    PBS 4.1 - kernel 6.14 - 2x10Gbit LACP, MTU changed from 9000 to 1500. PVE 9.1.1 - kernel 6.14 - 4x10Gbit LACP, MTU 9000 (i can't change it now) Still too slow: INFO: 43% (25.8 GiB of 60.0 GiB) in 26m 53s, read: 15.3 MiB/s, write: 2.4 MiB/s PBS is Dell R510 - 2 cpu - 32Gbyte - with 12x8Tbyte...
  4. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    I started to have problems upgrading PBS from 4.0 to 4.1; no any problem found with PBS 4.0
  5. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    Which PVE version are you using ? I have the last no-subscription with downgraded kernel too, but some vm is still very very very very slow... (i am testing only a few and less important vm). INFO: 67% (40.2 GiB of 60.0 GiB) in 49m 34s, read: 9.2 MiB/s, write: 0 B/s
  6. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    I have downgraded kernel on two clusters and PBS, so they are to the last software available (no subscription) but kernel 6.14.11-4-pve. One backup was normal, another one is still running, very slow; linux vm with guest agent: INFO: 32% (19.2 GiB of 60.0 GiB) in 23m 32s, read: 16.0 MiB/s...
  7. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    So, with a 9.1.1 node and 6.14.11-4-pve kernel, I can restore without any problem. PS: i had not problems with mass live migration, and I use always the same bond of 4x10Gbit with vlans and mtu 9000
  8. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    On a 9.1.1 node: uname -a Linux nodo4-cluster1 6.17.2-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-2 (2025-11-26T12:33Z) x86_64 GNU/Linux I use the same hardware for PBS and PVE (dell R730) and both with bond of 10Gbit ethernet on board (2 or 4), broadcom nextreme II. If the kernel's problem is...
  9. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    I have a slowness problem in restore too, and I can confirm that with a 8.4 host the problem disappear. Restoring with a 9.1.1 host, after a couple of minutes, i can see only one chunk per minute (or less), and now, for example, I have the restore process frozen at 35% (128Gbyte drive). PBS is...
  10. F

    [SOLVED] Super slow, timeout, and VM stuck while backing up, after updated to PVE 9.1.1 and PBS 4.0.20

    Same problem here; backups very sloooow and frozen, vm disk corrupted (more windows vms) with PVE 8.4 and PBS 4.1. So I have upgraded the cluster (6 nodes /ceph) to 9.1.1 and now i will wait, but: - I am in the middle of an upgrade, so 4 nodes are 9.1.1 and the other 2 nodes still last 8.4 - if...
  11. F

    Proxmox Backup Server 4.0 BETA released!

    [pbs-devel] applied: [PATCH] api types: make region regex less strict :)
  12. F

    Proxmox Backup Server 4.0 BETA released!

    Trying the first sync with my own ceph object storage cluster. I can confirm that doesn't accept "lt01" as a region (not important now), and I would like to know how much space is needed for the cache partition, because on the datastore summary info I see the cache available space and not S3...
  13. F

    Migrate a vm backup from a PBS to another

    Yes, sync jobs are one of the solutions, but for one time transfers I think that is better a simple command like "pbs backup transfer vmgroup destinationserver". Namespaces are great, but I don't know which vm I will transfer a day.... so grouping them is not possibile.