powersupport's latest activity

  • powersupport
    Hi, You don't actually need three separate jobs! Having multiple jobs for the same VM causes them to step on each other and prune each other's backups. The best solution is to use 1 single daily backup job and let Proxmox handle the retention...
  • powersupport
    Since the host is detecting both USB devices with lsusb, but they are repeatedly resetting and the VM can see them without any traffic passing through, it looks more like a USB passthrough or kernel regression after the PVE 9 upgrade rather than...
  • powersupport
    powersupport replied to the thread Live VM Migration fails.
    Hi, The error client closed connection to the resume command means that the migration data actually transferred successfully, but the QEMU process on the target node crashed or terminated immediately when trying to resume the VM state. Since...
  • powersupport
    Hi, Yes, to some extent. The best approach is to use a dedicated PBS API token with only the permissions needed to create backups, and do not grant delete privileges. Let PBS handle pruning based on its retention policy. However, if someone has...
  • powersupport
    Hi all, We are experiencing an issue on several Proxmox VE 9 nodes where management network connectivity is lost following a firewall failover, firewall reload, or temporary firewall service interruption on our Palo Alto PA1410 HA pair...
  • powersupport
    Hi, I can understand your concern. In your case, VM B is not really a separate machine but a refreshed copy of VM A, so keeping the same UUID would help avoid licensing issues and reduce administrative work. As far as I know, there is...
  • powersupport
    Hi, This sounds more like a hardware/BIOS issue than a Proxmox issue, since the system works fine after a full power off and only has trouble on reboot. You may want to check the BIOS boot settings again (especially Fast Boot / boot mode), and...
  • powersupport
    Hi, Unfortunately, this is currently not possible in Proxmox. The VM.Backup privilege allows users to view, restore, and also delete backups. There is no separate restore-only permission available at the moment.
  • powersupport
    When you delete a snapshot, Proxmox has to merge the changes back into the base .qcow2 file. Because it's on NFS, QEMU forces every single write to be completely synchronous over the network. This locks up the VM's disk controller and causes the...
  • powersupport
    powersupport replied to the thread Unable to remove a snapshot.
    Hi, It looks like the tape-restored snapshot may still have some locked or protected metadata. You may try: Running datastore verify Running garbage collection Checking for active tasks/locks Restarting proxmox-backup-proxy If normal removal...
  • powersupport
    Hi, This is expected in Proxmox. When a VM is shut down from the GUI, its disk is fully deactivated, so Veeam can’t see it. Using: qm stop 114 --keepactive works because it keeps the disk active even when the VM is off. a way to make...