powersupport's latest activity

  • 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...
  • powersupport
    Hi, Anyone advice on this issue? Thank you
  • powersupport
    This is results @alexskysilk root@pVE-04:~# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,vztmpl,iso lvmthin: local-lvm thinpool data vgname pve content images,rootdir lvm: pVE-DataStore vgname PVE-DS01 content...
  • powersupport
    powersupport replied to the thread Caching drive replacement.
    This looks more like a cache path / mount issue than an S3 problem. When PBS marks an S3 datastore as “unavailable,” it’s usually because the local cache directory isn’t accessible or doesn’t match what PBS expects. Here are a few things to...
  • powersupport
    Hi, This looks like the NFS storage is temporarily disconnecting during backup. Since it happens on different nodes and VMs, it’s likely a network or NFS mount issue, not the VM itself. Please check NFS connectivity, server logs, and mount...
  • powersupport
    We have set up a single-node Proxmox environment with storage backed by an FC LUN. Two storage types are configured on it: one as LVM and the other as directory storage. Recently, we attempted to migrate a VM from VMware to Proxmox. We tried...
  • powersupport
    This issue does not look like a CPU or RAM problem. The behavior you described (GUI freezing for 10–15 minutes and then recovering) is usually related to storage I/O delays. Since you have around 200 VMs, it’s possible that too many backups...
  • powersupport
    Hi, This usually happens when the server is a bit busy during the scheduled backup time. Since manual backups work fine, the issue is likely due to higher load when the automatic backups run. You can try running backups at a different time...
  • powersupport
    Hi, From the config, the VM is currently showing lock: backup, which suggests a previous backup task may be stuck. That alone can prevent new backups from progressing. Also, since the disk is QCOW2 on NFS and you’re using snapshot mode, it...
  • powersupport
    Hi Team, I have a question regarding the Proxmox version upgrade. Currently, our Proxmox is running version 8.4.0, and we plan to upgrade it to the last version of 8.4.x.However, because our security department does not allow us to grant...
  • powersupport
    Hi, You may want to check how your storage is configured first. In Proxmox, backups are usually stored as regular files (in the <span>dump/</span> directory), so there’s no direct GUI option to move them between storages. One approach you can...
  • powersupport
    Hi, The issue appears to be that your Windows Server 2025 VM is stuck in an Automatic Repair loop and unable to boot normally. Since the cloned VM is also showing the same behavior, this likely indicates OS-level corruption or a possible...
  • powersupport
    Hi, This is normal behavior. Even though the virtual machine is stopped and hasn’t changed, the system still needs to scan the whole disk during backup. However, it does not actually store or upload the full data again. Since nothing changed...