Recent content by Colin 't Hart

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 though. Turns out the remote site was using an old...

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 remote; is pushing on the primary better than pulling?

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 Management and FQ_CODEL. Any tips on configuring this?

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 Server configured as a remote but it's syncing...

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 noticed that the ethernet device names were different...

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?

Any Proxmox dev have any answer to my question?

Sorry, but *why* is this configuration information being stored outside of /etc ?

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...?

Thanks, that worked!

I'm a freelance Postgres DBA and use Proxmox to host a plethora of containers and VMs for work (research mainly) for my clients. It's been an absolute godsend, so a huge THANKS for making Proxmox! I found the new OCI support interesting, so I searched the OCI registry for "postgres" and chose...

So cpu type "host" makes Windows 11 significantly slower (see https://forum.proxmox.com/threads/cpu-type-host-is-significantly-slower-than-x86-64-v2-aes.159107/ ), but switching away from it you get a yellow warning flag in Windows Security for memory integrity. Is there no way to get both...

Fantastic!!

Just warning and booting anyway instead of erroring out would be even better! What's the worst that could happen?

I wonder if there's an easy way for you to provide a mechanism for us users to be able to "force" boot an unsupported distro. Many command line tools have "--force" options. In this case we have to resort to editing a packaged file to change the test. I wonder if you could have a "conf.d"...