Not really incremental backups

milosz

New Member
May 26, 2025
7
0
1
Hi,

I'm new to PBS but I love it.

My issue is that every incremental backup is full backup. File mailboxes.pxar is 639.82 GB. Reused 76.38 GB.

So every day I have "incremental" backup that is 640 GB, instead of 40 GB.

Here is log from backup client (backup of dedicated server):

Starting backup protocol: Tue May 27 11:55:44 2025
Using encryption key from …
Encryption key fingerprint: …
Using default master key..
Downloading previous manifest (Tue May 27 10:46:03 2025)
Upload directory '…' to '…' as mailboxes.pxar.didx
mailboxes.pxar: had to backup 563.44 GiB of 639.82 GiB (compressed 381.41 GiB) in 5229.90s
mailboxes.pxar: average backup speed: 110.32 MiB/s
mailboxes.pxar: backup was done incrementally, reused 76.38 GiB (11.9%)
Uploaded backup catalog (92.28 MiB)
Upload RSA encoded key to 'BackupRepository { auth_id: Some(Authid { user: Userid { data: "…", name_len: 4 }, tokenname: None }), host: Some("…"), port: None, store: "backups01" }' as rsa-encrypted.key.blob
Duration: 5230.99s
End Time: Tue May 27 13:22:55 2025

I would be grateful for any help.

Best regards,
Milosz
 
Hi,

Your backup in done incrementally :
mailboxes.pxar: backup was done incrementally, reused 76.38 GiB (11.9%)

But it seems that what you are backuping has a lot of changes.
Can you explain what exactly are you backuping ?

Cordialement,
Jean LANGBOUR I Technicien Support
 
Hi,

Your backup in done incrementally :


But it seems that what you are backuping has a lot of changes.
Can you explain what exactly are you backuping ?

Cordialement,
Jean LANGBOUR I Technicien Support
Thank you Jean for your response.

I'm backuping mail boxes. Yes, there is a lot of changes (new files added), bo existing files are not changing.

And this problem happens with all backups.
 
Hi,
you can try and see if the change detection mode metadata reduces your backup volume and runtime, see https://pbs.proxmox.com/docs/backup-client.html#change-detection-mode

Using this mode, the client tires to avoid re-reading and re-chunking content for already present and unchanged files as compared to the previous backup snapshot. Note that the first backup run using this mode will require reading all files nevertheless, as the split payload and metadata archive have to be created.
 
Hi,
you can try and see if the change detection mode metadata reduces your backup volume and runtime, see https://pbs.proxmox.com/docs/backup-client.html#change-detection-mode

Using this mode, the client tires to avoid re-reading and re-chunking content for already present and unchanged files as compared to the previous backup snapshot. Note that the first backup run using this mode will require reading all files nevertheless, as the split payload and metadata archive have to be created.
This looks very promise, thank you Chris, but it doesn't working. proxmox-backup-client backup vhosts.pxar:/var/www/vhosts/ --change-detection-mode=metadatashows help from proxmox-backup-client. without change-detection-mode backup is created. In allowed attributes there is no this attribute.
 
This looks very promise, thank you Chris, but it doesn't working. proxmox-backup-client backup vhosts.pxar:/var/www/vhosts/ --change-detection-mode=metadatashows help from proxmox-backup-client. without change-detection-mode backup is created. In allowed attributes there is no this attribute.
Then your client version is outdated, you probably need a more recent client version, at least 3.2.5-1
 
  • Like
Reactions: Johannes S
Then your client version is outdated, you probably need a more recent client version, at least 3.2.5-1
Yes, I don't have newer version.

Code:
 Package: proxmox-backup-client
Source: rust-proxmox-backup
Version: 1.1.14-1

But this version is in Ubuntu 20.04 repository… I can't find page where I can download newer package. Do you have any link to package or sources?
 
  • Like
Reactions: Johannes S
See the sources from where you can get the latest client version as described in the docs https://pbs.proxmox.com/docs/installation.html#client-installation
Unfortunately, still no success. I've done:

1. I've added deb http://download.proxmox.com/debian/pbs-client buster main to sources.

2. I've ran apt update.

3. I've got error The following signatures couldn't be verified because the public key is not available.

4. I've added [arch=amd64 trusted=true]

5. I've done apt search proxmox-backup-client and got proxmox-backup-client/stable,now 1.1.14-1 amd64 [installed]

6. There is no package proxmox-backup-client-static

7. I removed previously added repository: deb [arch=amd64 trusted=true] http://download.proxmox.com/debian/pve buster pve-no-subscription

8. I've added:

Code:
deb http://deb.debian.org/debian bookworm main contrib
deb http://deb.debian.org/debian bookworm-updates main contrib
# Proxmox Backup Server pbs-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pbs bookworm pbs-no-subscription
# security updates
deb http://security.debian.org/debian-security bookworm-security main contrib

but I cannot install proxmox-backup-client 3.x.x because I don't have a few packages in newer versions that are not present in Ubuntu 20.04.

10. I've again added to sources deb [arch=amd64 trusted=true] http://download.proxmox.com/debian/pbs-client buster main

10. I've ran apt search proxmox-backup-client and it's found in version proxmox-backup-client/stable 1.1.14-1

11. Still no success.
 
1. I've added deb http://download.proxmox.com/debian/pbs-client buster main to sources.
This should be bookworm, not buster.
3. I've got error The following signatures couldn't be verified because the public key is not available.
You will have to add the signing key as described in https://pbs.proxmox.com/docs/installation.html#secureapt
6. There is no package proxmox-backup-client-static
Since it is only available via bookworm, yes

but I cannot install proxmox-backup-client 3.x.x because I don't have a few packages in newer versions that are not present in Ubuntu 20.04.
You can use the statically linked binaries in that case, as it has no external dependencies. If the debian package cannot be installed (you can also use dpkg -i <path-to-deb> if you have downloaded the package), you can also extract the binary directly from the debian package archive (it's an archive which can be extracted with ar)
 
  • Like
Reactions: milosz