惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Help Net Security
大猫的无限游戏
大猫的无限游戏
雷峰网
雷峰网
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 聂微东
V
Visual Studio Blog
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
美团技术团队
有赞技术团队
有赞技术团队
云风的 BLOG
云风的 BLOG
Google DeepMind News
Google DeepMind News
Blog — PlanetScale
Blog — PlanetScale
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
博客园 - 三生石上(FineUI控件)
WordPress大学
WordPress大学
Vercel News
Vercel News
F
Fortinet All Blogs
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
小众软件
小众软件
月光博客
月光博客
A
About on SuperTechFans

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
PBS backup space grow up constantly
invalid@exam · 2026-05-29 · via Proxmox Support Forum

Hi, can someone help me to understand why the backup space increase contantly day by day?
I have two storage spaces for two different backup jobs, located to a NAS, PBS is a VM on my PVE cluster.
Every day for each vm I have 1 hour backup from 7am to 6 pm and at 9pm another backup.
After last backup I have prune to keep only last backup of the day and after that a GC to clear.
But the space increase day by day, the vm are the same, non tasks modification.

1779904448443.png

Looking at the screenshot, Prunes is 0 for both datastores. Are you sure you have set this up correctly?

Hi here you have:

1779910308240.png

And if you check a vm backup for example:

1779910395347.png

It seems all well done.

Hi,

Between your 2nd and 3rd posts, there is a huge difference. You should look at the prune log back in time to find out why the pruning was not happening, because your screen on the 2nd post is not "well done" like you thought (because you have 11 backups instead of 1).

Best regards,

Hi,

Between your 2nd and 3rd posts, there is a huge difference. You should look at the prune log back in time to find out why the pruning was not happening, because your screen on the 2nd post is not "well done" like you thought (because you have 11 backups instead of 1).

Best regards,

You have to look at 4th...

Hi,

Now you need to run the GC and wait 24h5min or 1445min (default setting).

Prunning doesn't free the space immediately, it's only the GC that can free the space.

And have you check your backup log to see the size of data backup ?

Best regards,

Hi,

Now you need to run the GC and wait 24h5min or 1445min (default setting).

Prunning doesn't free the space immediately, it's only the GC that can free the space.

And have you check your backup log to see the size of data backup ?

Best regards,

As I wrote, I run GC avery night... but the curve grow up as you can see, why?
Can I provide you some logs to understand?
Vm are the same, just one has a small database but modification by day are very small, many other vm has no data incremets or better, only os maintenace like updates and so on.
But on my side it's quite stange this constant growth

GC work fine as each day:

1779914886847.png

Hi,

You should really check the backup log to have the exact data size.

For VMs with small data changes (as you said), 50 to 70GB a day seems a lot to me, or you just don't know that your VMs really have a high data change, and therefore your deduplication factor should be pretty low.

And for last, only the log can help; the screen of the WebUI is pretty much useless.

Best regards,

Hi,

You should really check the backup log to have the exact data size.

For VMs with small data changes (as you said), 50 to 70GB a day seems a lot to me, or you just don't know that your VMs really have a high data change, and therefore your deduplication factor should be pretty low.

And for last, only the log can help; the screen of the WebUI is pretty much useless.

Best regards,

Can I send you logs for a backup cycle?
I can't really understand why this constant growth...

Please show the summery page, again.

UdoB

Distinguished Member

In your first screenshot there is "Prunes 0". Is this still the case?

You may trigger pruning manually via "Run now" - and watch the log live.

Are namespaces involved? The "Edit: Prune Job" has a "Max. Depth" setting. If this is set to low it may ignore sub-namespaces.

increasing space usage like this can also be caused by VMs not freeing up unused space properly (i.e., not discarding it). VM backups happen on the block layer - the full VM virtual disk is backed up. if applications inside the VM do a lot of temporary writes, they might dirty a lot of the disk even though within the VM it looks like most space is unused. I'd check the backup task logs to see if there are VMs that have an unexpectedly high rate of change. of course it could also just be natural growth over time - e.g., log files/state/.. accumulating inside the guests.

Please show the summery page, again.

Hi here you have.
It's taken now after a manual prune/GC run yesterday evening
I think it's a bug that prune it's not counted.

1779954776056.png

In your first screenshot there is "Prunes 0". Is this still the case?

You may trigger pruning manually via "Run now" - and watch the log live.

Are namespaces involved? The "Edit: Prune Job" has a "Max. Depth" setting. If this is set to low it may ignore sub-namespaces.

Hi, if you read the posts... I've done it.

"Are namespaces involved? The "Edit: Prune Job" has a "Max. Depth" setting. If this is set to low it may ignore sub-namespaces."
I'm not sure to understand well.
This is my config, it seems not set.

1779954987880.png

UdoB

Distinguished Member

This is my config, it seems not set.

Correct. That default is fine!

But you have configured an explicit NS "BKP-Pol-One-VM". Dig at this fact, it may be the reason for the confusion...

You could remove that explicit Namespace here and Prune the whole Datastore "BKP-Pol-One"!

Last edited:

Increasing VM sizes like Fabian said seems plausible.

But it doesn't explain the prunes not being registered in the Task Summary. Might be some permission/namespace mismatch? Although your prune logs don't show any error and the garbage collects are being registered.

Then again, disk filling up is actually more of a garbage collect issue than a prune thing. Did you already look into those?

Last edited:

Correct. That default is fine!

But you have configured an explicit NS "BKP-Pol-One-VM". Dig at this fact, it may be the reason for the confusion...

You could remove that explicit Namespace here and Prune the whole Datastore "BKP-Pol-One"!

I don't understand, Namespace are created to organize backups, what is wrong?

UdoB

Distinguished Member

I don't understand, Namespace are created to organize backups, what is wrong?

Nothing.

But we are debugging the "Prune 0" shown on the dashboard. It does not feel right, correct? Perhaps it is a "display"-error in the sense that it shows the number of prunes for the Datastore but not if there is only pruning only of a (sub-) namespace.

I am just guessing, I did not test/verify that...