Search results

Now installed 6.3-3 and no updates at this moment.

But it was not fixed in updated version

Still was not available in enterprise. When this bug will be fixed?

When it will be available?

Thank. I'll wait.

Example pvesh set /cluster/backup/7a53d4455a95556981da13e2e1836f4595fffcff:5 -starttime 0:0 -all 0 -bwlimit 50000 -dow sat -enabled 1 -ionice 8 -lockwait 60 -prune-backups keep-last=3 -vmid 14766

root@nl-518:~# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.41-1-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.73-1-pve: 5.4.73-1 pve-kernel-5.4.41-1-pve...

Anyone?

-prune-backups keep-last=3 this option work for vzdump, but does not work for backup job. Why? How to set a backup limit?

We can't update a backupjob with option -maxfiles 3 or -prune-backups keep-last=3 using the API. The system return: error during cfs-locked 'file-vzdump_cron' operation: value without key, but schema does not define a default key How to fix it? This is some bug, we can't work...

Great! It works. Thank you so much.

I have no any updates. And I have qemu-server: 6.1-5 now.

Today I updated Proxmox and can't clone VM using the API. Return an error "no such cluster node ' '". I do not have cluster. And I can clone VM using the GUI. How to fix it? root@nl-460:~# pveversion -v proxmox-ve: 6.1-2 (running kernel: 5.0.21-4-pve) pve-manager: 6.1-7 (running version...

Did you use the correct interface? Try to use other.