Recent content by hermelin

and is something info about fs-freeze in logs on VM

Do you use qemu-guest-agent ? https://pve.proxmox.com/wiki/Qemu-guest-agent

Sorry, size of subscription window is ok, I think that so big window is too big for subscription info. Thanks I think that subscription window will be renamed and contains tasks with errors and warning etc. I think something like this https://dsmorse.github.io/gridster.js/

You can double-click on item too.

Hi, I have few recommendations pro better dashboard: Window Subscription is too large - I think that icon or button in head panel will be better. Window Running tasks rename to Tasks. It will contain history all tasks (for example few days) and running task will be upper in list and will has...

Hi, so I think that proxmox-backup-client is not suitable for disk with many files and bigger capacity over TBs ? Because incremental backup is running for hours, rsync make incremental in minutes. But PBS is great for backup of VMs

Hi Thomas, thanks for reply. Yes, this is solution. But I think that protection against overload server with enabled Skip verified snapshots will be good :). Thanks for your job. Best regards Zdenek

Hello, I have recommendation for improve verification (or backup and restore too). I have enabled "Verify New Snapshots", so after backup is started verification immediately. But backups are make quickly (dirty bitmap etc.), so I have backuped about 15 virtuals in 10 minutes. But then after that...

solved https://forum.proxmox.com/threads/certain-vms-from-a-cluster-cannot-be-backed-up-and-managed.57016/page-5#post-272544

Yes, you need shutdown and start again the VMs. Or maybe help hibernate and start, but this I didn't test.

I do tracing too, but tracing freeze about time when scheduled backup started backup VM syslog message backup log So can be some relation with services started in this time

I am upgrade to 6 using https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0. All packages are sucessfully upgraded to Buster and Proxmox 6 packages upgraded too without problem. NoVNC console is working if I newly start VMs, but after some time of running VMs appear the problem. So it doesnt...

Yes, I tried Chrome and Firefox - same problem.

After yesterday backup many VMs error like this: VMs are running, but don't work noVNC console and backup. It look's like problem with qemu-server sockets, may be.

I have some VM on LVM, some on LVM-thin. On both is this behaviour. Last backup was correctly on one VM which hasn't function with noVNC, but other VM backup with unfunction noVNC was failed.