Recent content by Bu66as

Hi @bbx1_, Your output shows the core problem: the frr.service was inactive. The status output also shows the service is disabled (Loaded: ...; disabled; ...), which is why it did not start automatically after you rebooted the nodes. You should enable the service to start on boot on all...

Die RAID-Z-Erweiterung inklusive Rebalancing ist zwar Teil von OpenZFS 2.2, wurde aber als "Technology Preview" klassifiziert und ist standardmäßig deaktiviert. Proxmox hat diese experimentellen Funktionen in den pve-Paketen nicht standardmäßig aktiviert. Du müsstest OpenZFS manuell mit der...

This isn't configured in the restore wizard itself, but on the backup repository. You don't need to recreate the workers. The server that mounts the backup for a file-level restore (the Gateway Server) determines which virtualization platform it can use for the helper appliance. Your repository...

Hello @eisvleo, For scripting without a password prompt, you should use API tokens. Create a new user in PBS with the necessary permissions on the datastore (e.g., the DatastoreBackup role) and generate an API token for it. You can then define the repository and the token in your script via...

Hello @iprigger, to verify what @Stoiko Ivanov mentioned, could you please check the raw source of the report email? This would show whether a MIME part with Content-Type: text/html is actually included or if it's missing entirely.

Yes, unfortunately I got confused when pasting.

yes :eek:

Dass die VMs auch mit aio=io_uring auf dem neuen Kernel erst einmal ohne sichtbare Fehler starten, ist trügerisch. Das Problem sind potenzielle Deadlocks oder Datenkorruption unter I/O-Last, die nicht sofort auftreten müssen. Wie von @gurubert ursprünglich angemerkt, ist die Umstellung auf...

Hello @BvE, your assumption is correct. After you set issue_discards = 1 in /etc/lvm/lvm.conf, you can apply the changes without a reboot by running vgchange --refresh.

Hello @bacbat32, While @SteveITS is right that WAL/DB can contribute to the raw usage, the 1.8 TiB of STORED data seems to be caused by the ~900k objects that your initial rados -p ceph-hdd ls command showed. Since rbd ls is empty for that pool, these are likely orphaned objects from disks that...

Hello @jnthans, glad the plugin update worked for you. Regarding the incorrect Hyper-V helper issue that @AndreasS mentioned: This usually points to the Backup Proxy configuration. It's worth checking which proxy is set for the Proxmox environment and ensuring a Linux proxy is available and...

Hello @kobold81, could you please post the configuration file of your VM? You can find it at /etc/pve/qemux-server/VMID.conf (replace VMID with the actual ID of your virtual machine). It's possible that the disk controller type (e.g., SATA, SCSI, VirtIO) has changed after the restore.

Hello @bacbat32, While @SteveITS is right that WAL/DB can contribute to the raw usage, the 1.8 TiB of STORED data seems to be caused by the ~900k objects that your initial rados -p ceph-hdd ls command showed. Since rbd ls is empty for that pool, these are likely orphaned objects from disks that...

Hello @pvpaulo, @shanreich is on the right track. The different configurations are almost certainly caused by the vlan-aware flag on your vmbr0 on node PVE01. If that bridge is set as VLAN-aware in /etc/network/interfaces, SDN correctly omits the ln_* and pr_* veth pairs because they are not...

Hello @alexandere, the method shown by @Moayad using pct set <CTID> --nameserver <IP> is the correct way to make the DNS setting permanent. Normally, the DNS server should be automatically adopted from the host settings during the container's creation. This behavior indicates a problem with the...