Search results

I ended up not attempting to perform the change. For now I am holding with what I have (although I don't have much room left) and I plan on creating a new cluster from scratch, as it will also serve to overcome the 32 MAC addresses limitation per NIC that Hetzner imposes on their vSwitches (I...

Anyone has information about this that could confirm the procedures explained above, and shed some pros and cons?

I have read on the forums that it is convenient (necessary?) not to have HA in use, albeit I don't really know why, as I have not found anything on the official documentation regarding this. What the documentation warns about is not to have replication on, but I am not sure why, as the node...

Hey everyone! So I have a 7-node cluster of PVE 7.4 and I need to reinstall one of the nodes because I did not REDACTED when installing it. I would like to keep the same IP address and hostname. The node is already empty (i.e., all LXCs and VMs have already been migrated to another node) and HA...

Hi, @Moayad, and thanks for your reply. I wasn't aware of the possibilities explained in the link you provided. However, if I understood correctly, creating the file /etc/.pve-ignore.resolv.conf would prevent Proxmox from updating the file /etc/resolv.conf with the DNS configuration made for...

Oh, you meant the LXC. I thought you meant the node. In that case, yes, you connect to the LXC via the WebGUI terminal or SSH and you run the commands.

Hey everyone! So I have a number of LXC in my Proxmox cluster, some of them Debian 11 and some others Debian 12 (templates provided by Proxmox), and I am trying to find a way to clear the local DNS cache as I need to force querying again the internal DNS server despite the TTL of the record. I...

You either use the classic apt-get update && apt-get dist-upgrade console commands or you use the WebGUI, by selecting each node of the cluster and going to the Updates menu option.

Hey everyone! So I have a server at OVH in France and just installed a Debian 12 Bookworm using their installer. And I started the installation of Proxmox Backup Server 3.0.1, just as I did a few days ago on a Debian 12 Bookworm on a server at Hetzner in Helsinki (one will be the replica of the...

By the last usage data points, do you mean the total size on disk for all backups, not taking into consideration what is a backup, what is a snapshot and the deduplication level achieved over time (and, therefore, presumed to be achieved in the future)? Moreover, from your words I presume that...

Hey everyone! Quick question: the Estimated full column for a given datastore in the Dashboard: Datastore usage takes the retention policy into consideration when calculating the expected time until the disk is full? I assume it is statistically computed given the deduplication level that has...

HI, @czechsys, and thanks for your reply. Yes, one of my pending tasks is to disable systemd-timesyncd and install and configure Chrony. It just never manages to move to the top of that list, heh :) Regarding setting up a NTP server, I take it that it would have to be a physical machine, but...

Hey everyone! As far as I understand, my Proxmox 7 cluster, installed on top of a Debian 11 Bullseye, uses systemd-timesyncd to keep the clock in sync via external NTP servers, configured either in /etc/systemd/timesyncd.conf or in a separate file inside /etc/systemd/timesyncd.conf.d/. All of...

I agree. I opened a feature request bug report instead. Not that I could not open dozens of them, come to that, but I think this one is a must these days.

No worries. I'll keep the extra rule in the security group for the time being. Thanks for the reply! P.S. I guess I am better off not hacking those rules in /usr/share/perl5/PVE/Firewall.pm, or is it just that they will be overwritten with each update?

Hey everyone! Quick question: Does the HTTPS macro of the PVE Firewall include UDP traffic (to port 443) or is it still just TCP? I am on PVE 7.4-17, but if it is available in PVE 8.x I would also be interested in the answer, since I plan on migrate to it soon. Thanks in advance.

For future reference, Fabian means this: the problem is that the upper layer doesn't know whether the lower storage layer uses compression and how much it affects the data. Still, my request would be to enable such information to be exposed. Not urgent, not critical, but when possible :)

I think that is an excellent idea, @BruceX. Any chance this warning message could be brought into the next version of Proxmox, @fabian? Once you've experienced the situation, it makes sense and you will probably not fall for it again, but for the first-timers it could be very helpful. :)

I like this idea as it is quicker (no need to do a remote call to the API). On the other hand, calling the API ensures that, were the guys behind Proxmox change the behaviour in the future (e.g. the method were to perform some other tasks), it would still be valid. Thanks for the heads-up!

I use ZFS in two of the five nodes. Especifically, the one that had the filesystem corruption was using both SSD disks using software RAID 1 with ext4 and also ZFS disks in RAID 1. I had LXC on both storages, and all of them suffered from corruption. Unfortunately, I never managed to figure out...