Conflicting maxfiles policy and retention period

[MrHackCZ]

Hi there. Same problem here - I think it is bug. I have this settings:

root@proxmox:/var/log/pve# cat /etc/vzdump.conf |grep -v ^#
maxfiles: 8

root@proxmox:/var/log/pve# cat /etc/pve/storage.cfg
dir: local
    path /var/lib/vz
    content vztmpl,snippets,iso
    maxfiles 0
    shared 0

lvmthin: storage
    thinpool vmachines
    vgname proxmox
    content rootdir,images

dir: backup
    path /mnt/backup
    content backup,iso
    maxfiles 8
    shared 0

In vzdump.cron is still maxfiles 10 (last time value)

root@proxmox:/etc/cron.d# cat vzdump
# cluster wide vzdump cron schedule
# Automatically generated file - do not edit

PATH="/usr/sbin:/usr/bin:/sbin:/bin"

30 0 * * *           root vzdump 100 101 --mailnotification failure --compress zstd --node proxmox --remove 1 --mode snapshot --storage backup --maxfiles 10 --quiet 1

If I change maxfiles in cron to value 8, and change time of backup eg. to 00:45 maxfiles is still setup at 8. Changing values in storage.cfg / vzdump.conf doesnt matter.

 

[fiona]

Hi,
do you also have unwanted Erase data jobs in your task log?

The different maxfiles settings will not update one another.

vzdump gets the value for maxfiles in the following order (only if no value is found at a stage, it will continue looking):

1. value from the CLI/cron job
2. value from the storage configuration
3. value from/etc/vzdump.conf
4. the value 1

When you create a new job, the maxfiles option should not be set for the cron job. If you remove the --maxfiles 10 from your cron job, the maxfiles 8 from the storage configuration will be used instead.