/etc/vzdump.conf parameter remove: <boolean> (default = 1)

psionic

Member
May 23, 2019
75
9
13
When using the 'Backup now' feature in the Container GUI, the following parameter in /etc/vzdump.conf does not work:

remove: <boolean> (default = 1)
Remove old backup files if there are more than maxfiles backup files.

I have the parameter set to 'remove: 1'

If the set max files is reached, the process stops with an error instead of erasing the oldest backup:

ERROR: Backup of VM 105 failed - There is a max backup limit of (5) enforced by the target storage or the vzdump parameters. Either increase the limit or delete old backup(s).

Is there a fix for this?
 
Hi,

hmm, true it is actually even a bit weirder:
The webinterface hardcodes the remove parameter to 0, as API/CLI parameters have the highest priority your change to vzdump.conf will be ignored.

On the CLI one can use the parameter to enable or disable it. But there the default is "remove: 1", and if one sets it to "0" in the vzdump.conf it is ignored also (if the explicit "--remove 0" isn't passed along to vzdump)..

I get that we really want to default to "not remove" for webinterface triggered jobs, as that's just more safe, but there should be some way to allow people with enough permissions to enable the "purge older backups" logic..

Can you please open such an enhancement request over at our Bug and Feature tracker: https://bugzilla.proxmox.com/
 
  • Like
Reactions: psionic
Hi,

hmm, true it is actually even a bit weirder:
The webinterface hardcodes the remove parameter to 0, as API/CLI parameters have the highest priority your change to vzdump.conf will be ignored.

On the CLI one can use the parameter to enable or disable it. But there the default is "remove: 1", and if one sets it to "0" in the vzdump.conf it is ignored also (if the explicit "--remove 0" isn't passed along to vzdump)..

I get that we really want to default to "not remove" for webinterface triggered jobs, as that's just more safe, but there should be some way to allow people with enough permissions to enable the "purge older backups" logic..

Can you please open such an enhancement request over at our Bug and Feature tracker: https://bugzilla.proxmox.com/
Bug 2745 - /etc/vzdump.conf parameter 'remove: <boolean> (default = 1)' does not work
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!