Recent content by bennetgallein

PBS nutzt fuer S3 einen lokalen Chunk-Store als Cache damit eben nicht auf die (potentiell) unverlaessliche S3-API gewartet werden muss, die performance von S3 an sich sollte daher erstmal sekundaer sein und wird ja auch in den Benchmarks ueberhaupt nicht betrachtet...

in dem iperf sieht man auch ein paar Retransmits (Retr Spalte), ich denke die Netzwerkverbindung hat vlt. einen guten Durchsatz, aber einfach keine wirkliche Stabilitaet. Am besten schaust du mal mit "mtr" wie viel Paketverlust du tatsaechlich zwischen dir und Hetzner hast. Da waere dann...

Hi, i have a similar error: 2025-10-11T17:00:02+02:00: sync group vm/105 failed - while reading snapshot 'BackupDir { store: "xxx", ns: BackupNamespace { inner: [], len: 0 }, dir: BackupDir { group: BackupGroup { ty: Vm, id: "105" }, time: 1760194800 }, backup_time_string...

Facing the same mental struggel to convert between units when debugging networking issues, I've build a small little Requestly (https://requestly.com/) middleware that just multiplies by 8. https://app.requestly.io/rules#sharedList/21aff97d086747c3aa9b968d19a6b8e1-Proxmox-netin-out-to-bytes

To add to this, I'm trying with hetzner S3 storage and the region "hel1" is not accepted by any inputs (or manually editing via config). root@pbs:~# proxmox-backup-manager s3 check hetzner 6892495451 --store-prefix / <Error><Code>LocationConstraintConflict</Code><Message>The location constraint...

Important thing is the bugzilla tracker: https://bugzilla.proxmox.com/show_bug.cgi?id=2943

I see, thanks!

Hey everyone, looking for some insight how to cleanup the following situation: I have a datastore that had backups, but all were removed. Garbage Collection ran successfully but there are still files and chunks leftover. This is the output of the GC: 2025-06-13T11:37:53+02:00: Access time...

Great release, especially exited about the GC stuff and the binary client. Where can we find the download to that? nevermind: https://pbs.proxmox.com/docs/installation.html#client-installation

is there a bugtracker ticket or anything in the mailing list to help test when it comes around?

You will loose deduplication when seperating into different datastores. Let's wait for a Teammember to say something about the 19m chunks. From the docs (https://pbs.proxmox.com/docs/technical-overview.html) there's no limit mentioned somewhere

Since you are on using NVME SSDs you can also see and try if sync-level=file fixes your issue. What's probably also interesting is the Controller you are using inside the server and if there are perhaps any hardware errors in dmesg

From this post: https://forum.proxmox.com/threads/proxmox-backup-server-2-3-1-1-stuck-after-backup.119854/ Perhaps the thread can help you

When you check the PBS server, are there any running validation jobs? Depending on your storage backend (e.g. ZFS) you might want to disable "Verify new backups" on the datastore settings, since they consume quite a few resources and can quickly overload the server if multiple are running.

Hi, it already _is_ possible, but it's a bit of a pain, since neither the GUI nor the CLI commands seem to be working (correctly). To add PBS: 1. Open the /etc/proxmox-datacenter-manager/remotes.cfg file 2. Add your desired paragraph: pbs: fsn1-1 authid connect@pbs!connect...