Search results

We ecnounter the same error in a multi-node pve cluster with an external ceph. to give this topic more traction, let's check if there are more things in common... we're on the following version: # pveversion -v proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve) pve-manager: 8.2.2 (running...

Thanks for the update. The 5.27TB value comes from the dashboard or any command from the cli? It may be different depending on the filesystem/storage below, that's why I'm asking.

It looks like you didn't install corosync-qdevice on each Proxmox VE node. apt update && apt -y install corosync-qdevice and then try again.

Yes, you can do that and I'd recommend keeping 3 MONs and MGRs. Please keep in mind that if you lose one server, Ceph will immediately recover the missing objects on one of the remaining nodes. that leads to a higher storage usage and can lead to full OSDs. It depends on your goal: - if you...

If your prior backups use zstd for compression, you should calculate about the same for the first backup on the pbs. Each subsequent backup can then be deduped and only needs to store additional chunks. If you have multiple VMs with the same chunks, dedup can even be applied on the first backup...

Are these numbers always there and always like this? do you use some kind of automated snapshot mechanism and slow, rotating disks in your Ceph?

Prima, danke für's Bescheid geben :).

Ja, liegt auf jedem Proxmox Server unter /usr/share/doc/pve-manager/examples/vzdump-hook-script.pl in der zum Proxmox Server passenden version vor. Da kannst du schauen welche Events es gibt.

The still running VMs use the old QEMU. After shutting down and starting your VMs, they run with the updated, current QEMU version and fleecing should work.

I was referring to https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvesdn_support_status (See 12.2.2) but I agree, it seems to be supported.

Please post your VM config. You may try to set your IO scheduler from io_uring to native for this VM and test again. May help, may not ;-). Please report back if possible.

1. The target ratio is expressed as 0.9 (for 90%). You did it right. 2. I'd recommend setting the autoscaler to on and let it do it's magic - except you want to put lots of data on your pools in the next days or your storage usage varies heavily within short time frames That leads to up- or...

Let me show an example: 1 Server with 1 CPU consisting of 2 Cores/4 Threads can host dozens of VMs. But keep in mind that you should only use a maximum of 4 Cores per VM. So yes, you can use many more virtual CPUs in all your VMs as you have threads in your CPU.

Sieht doch schon mal gut aus. Ich würde vermutlich eher job-init und job-end verwenden. job-abort sollte ebenfalls nicht ignoriert werden, falls der backup job mal nicht aufgrund eines fehlers zu ende läuft.

Did you reload your web gui after rebooting?

Thanks :). The command should be qm guest cmd <vmid> .... Maybe you want to edit your post.

Congratulations :) Is the esxi importer already available in the enterprise repo?

ssh on the host must not be disabled. Protect it by using ssh keys for logins and prohibit logins with passwords and/or use the built-in firewall to protect your host.

Ich würde den Ansatz mit dem Hook-Script verfolgen. Unmöglich ist nichts, aber VMs und Hypervisoren sollten sicherheitstechnisch voneinander getrennt sein und ein Zugriff aus der VM auf den Hypervisor ist normalerweise nicht wünschenswert. Umgekehrt, von Hypervisor zu VM lässt sich sowas mit...

The Proxmox VE Node doesn't care if ssh is active on your VMs or not. May it be an option to use key-based authentication only and don't allow logins using passwords?