Recent content by carles89

Hi Lukas, Before trying anything, I've upgraded to PDM 1.1, but the issue persisted. systemctl stop proxmox-datacenter-api.service rm /var/cache/proxmox-datacenter-manager/remote-tasks/state systemctl start proxmox-datacenter-api.service That did the trick! Tasks are showing now. Here's...

Same here, we've a PDM instance connected to several remotes, and in one of them we cannot see all completed backup tasks listed on PDM. It seems random, some tasks show, some tasks don't. All of them appear on PVE side (as completed). PVE Version: pve-manager/8.4.19/a68fb383814bb1e6 PDM...

You can switch to no-subscription repository, do apt update, install the desired kernel doing apt install proxmox-kernel-6.xx (input your kernel version here), then go back to enterprise repository and do apt update again. Make sure you only install the desired kernel and anything else when in...

I'd recommend Opnsense. It fits all these requirements and it can be installed as a VM on Proxmox VE (just download the iso-vga installer) https://opnsense.org/ It's basically an open source firewall. Among other functions, you can create scheduled firewall rules (to block traffic at certain...

If everything works as expected with a previous kernel, an option would be to install PVE 9, pin [0] the kernel that works (i.e. 6.14) and then upgrade to PVE 9.1. If it works, you could pin the same kernel on the rest of the nodes before upgrading. It seems 6.17 is giving some trouble both...

6.14 resolved it for us too. We're doing backups since Monday without issues.

Same here, but with fully updated PBS 4.1 and enterprise repos. The server is an HP DL360 Gen10+, and the RAID controller an HP MR416i-a Gen10+. When the server hits the issue, we have to do a hard reset since some processess get stuck in D state and it's impossible to finish a graceful...

We're also testing the new Fabrics GUI and we see exactly the same behaviour with pings, even with a single fabric. Tested lots of different configurations, and the only one that makes it stable is setting node's /32 ip address to every interface that belong to the fabric, as per @ggoller...

I understand. To me, it seems these are two different approaches to avoid running out of space. With quotas, one just needs to make sure other datasets don’t consume all the available space (that’s why I apply quotas to all datasets). Otherwise, write operations may fail (even if the quota is...

Why not use zfs quota? Maybe I'm missing something, but seems like a simpler approach to me (see: https://forum.proxmox.com/threads/proxmox-backup-server-3-1-2-set-zfs-quotas.139917/post-625317). I set up a quota for each dataset and call it a day.

Have you tried by recreating the EFI disk? https://forum.proxmox.com/threads/vm-reboot-issue-vm-stuck-on-proxmox-start-boot-option-screen.154925/post-712527

As per the documentation[0]: Adding/Deleting Nodes After QDevice Setup If you want to add a new node or remove an existing one from a cluster with a QDevice setup, you need to remove the QDevice first. After that, you can add or remove nodes normally. Once you have a cluster with an even node...

Hi, vlan111 has an incorrect vlan-raw-device. It should be vmnetbr, not vlan111 itself. Currently, vlan111 is not linked to the physical interface through the bridge, so it won’t work.

Maybe you're hitting this bug: https://forum.proxmox.com/threads/veeam-silent-data-corruption.155212/post-718208, have you tried with the last version of PVE plugin for Veeam?

You have to click on "Reissue" in order to free the license from the old server. Then, add it to the new server.