I'm still not convinced the current sync protocol can't be improved to take advantage of rsync-like smarts. But maybe it's just me not being used to how long the initial syncs take.
I did manage to find a few areas for improvement in our infra...
I just realised that all the traffic is double-encrypted as it's going over inter-site VPN too. I can make the traffic go directly over the Internet and see if that helps.
Currently it's receiving about 24mbit.
Right now I'm pulling on the...
No limiting in the routers at each end. They are both EdgeRouter X. The overall speed is limited by one end being 100mbit. We've never noticed any sort of slow speeds in these fantastic little routers.
I notice that it supports Smart Queue...
Hi,
We're wanting to replace a somewhat home-grown backup solution based on rsnapshot and rsync with Proxmox Backup Server. The rsnapshot solution uses rsync to mirror the backups to other servers, including one off-site.
I have Proxmox Backup...
And I came here after I installed PBS on top of an existing old-many-times-upgraded Debian install. The network interface wasn't initialised as it should. It turned out to be a different issue, but when I compared it to my new PBS install, I...
AFAIK /etc/systemd/network/ is a good place for .link files - /etc/ really is the first place i would look for them.
(We've had it there since 7.x and still in 9.2; we pin manually with more insightful names than the pinning tool nowadays...
I came here to ask the question about whether there is a good reason that I shouldn't move my .link files to /etc/systemd/network (which is where the man pages seem to suggest they should be anyway) so I was pleased to find this thread at the top...
No real opinion for me, as long as all config files are under /etc somewhere for grepability, backupability, etc. And this file is generated by the installer so there shouldn't be any preexisting files?
Iirc, one reason was to prevent clashes with potentially pre-existing configuration files in /etc. We could maybe implement specifiying the base path for the generated files to circumvent that and enable generation of the link files in /etc?
Hi...
I am using pve-network-interface-pinning to pin enp1s0, for instance, to eth0, eth1... and so on.
I have 9 nic each server.
But I need to change the hardware and after that, all nic turns back to previously name, like enp1s0, when I use ip...
We are excited to announce the release of Proxmox Virtual Environment 9.2. This release focuses heavily on platform refinement, stability, and core optimization.
Proxmox VE 9.2 is built on the robust Debian 13.5 "Trixie" and ships with Linux...
We're pleased to announce the release of Proxmox Backup Server 4.2.
This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable...
I was getting this in Debian 13 web server hosted inside Proxmox 9.1.7
Running `uptime` yielded a clue:
Mounting the proc filesystem as suggested solved the problem, but why haven't I run into this before...?