If you see 4GiB less of memory in the node summary, then they are used for something else. But Proxmox VE won't be able to use them.
So overall, another ~2 GiB of memory used doesn't surprise me too much.
Regarding the mismatch of seeing 60GiB of...
Can you share a few more details? For example, which summary shows 46 GiB? The one in the node summary?
Keep in mind that other services on the host also need memory. For example the whole management stack that handles the guests, provides the...
Is the Balloon Device checkbox active in the VMs Memory configuration (Advanced section)?
Is the Balloon Service installed and running in the Windows VM?
The Balloon Device is needed to communicate with the VM regarding its memory usage (and...
schau mal obs in /etc/pve/nodes noch Ordner von den alten Nodes gibt. die kannst du sicherheitshalber mal wo anders hin verschieben bevor du sie ganz löscht.
The main issue that happens here is if the backup target (storage, network, ...) is not fast enough to ACK a write. As the backup will halt the write operation of the VM until it got the ACK that this part of the VM disk in question has been...
well, that is setup that is not officially supported, so there might be some edge cases and we don't have a lot of experience with it.
regarding the /run/pve directory: is there a chance that the permissions are not as expected on some level...
The problem is that this node is part of a cluster, but cannot connect on any of the both networks to the remaining cluster:
The result is that the service/protocol for the cluster communication is not working and as a result of this, the...
Can you show the contents of your storage.cfg? cat /etc/pve/storage.cfg.
Paste the output within CODE tags for readability, or use the format buttons at the top of the editor.
well, that looks like a local DNS resolver/forwarder (10.1.1.7). Where does it get its results? Take a look there to figure out why it won't respond with v4 results.
seems to be working fine here:
dig +short de3.cdn.proxmox.com @1.1.1.1
45.84.67.184
dig +short fr.cdn.proxmox.com @8.8.8.8
51.91.38.34
Is your DNS setup maybe the cause?
maybe, never tried it. it is definitely more complex and chances are that things go out of sync in the ceph config if you are not careful. or versions might differ a bit between the ceph mons.
if things go wrong and you run a unique setup like...
Wie ich schon versucht habe zu erklären, ist der große Unterschied von PVE 8 → 9, dass die Host Sicht des RAM Verbrauchs jetzt deutlich richtiger berechnet wird. Unter PVE 8 war der Wert mitunter deutlich zu niedrig.
Das Balloon Device zu...
Okay. For the initial sync, you could have either used a "Removable Datastore", sync to it, move it to the remote location, add it there as well and then sync from it to the local remote datastore...
TIL about gdu. Deutlich flotter als ncdu. :)
@TErxleben je nachdem wie alt der Host ist und was da abseits von PVE irgendwann mal drauf installiert wurde, kann auch ein apt autoremove und apt purge manchmal ganz gut tun. Auch alte Kernel...
Thanks for the tip. We added the IPs of the clusters to the firewall, and it worked! Just had to map the server names to the private network in /etc/hosts to force the migration over the PVN, and use detailed mapping, and everything went as...