[SOLVED] Max Backups ignored

RobFantini

Famous Member
May 24, 2012
2,009
102
133
Boston,Mass
we have
/etc/vzdump.conf :
Code:
maxfiles: 2

/etc/pve/storage.cfg
Code:
cephfs: cephfs
        path /mnt/pve/cephfs
        content backup,iso,vztmpl
        maxfiles 2

yet after the backups done last night we have 3 dump files per vm .

this was not the case before this weeks debian package upgrades.

perhaps there is a bug to be reported?

we do use a custom script . so perhaps there were changes to vzdump and it is not getting parameters correct.

does anyone else see maxfiles ignored?[/code]
 
hi,

it's working normal here.

can you send the output of pveversion -v
 
Code:
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-5 (running version: 6.1-5/9bf06119)
pve-kernel-5.3: 6.1-1
pve-kernel-helper: 6.1-1
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.3.10-1-pve: 5.3.10-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph: 14.2.5-pve1
ceph-fuse: 14.2.5-pve1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-15
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-4
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2
 
we do use a custom script . so perhaps there were changes to vzdump and it is not getting parameters correct.

what about your custom script? what does it do? could you post it here (if you're allowed)?
 
and here is output from backup log
Code:
vzdump 105 --mailnotification always --mode stop --compress lzo --quiet 1 --mailto rob --storage cephfs
  
  
  105: 2019-12-23 15:02:02 INFO: Starting Backup of VM 105 (lxc)
  105: 2019-12-23 15:02:02 INFO: status = running
  105: 2019-12-23 15:02:02 INFO: backup mode: stop
  105: 2019-12-23 15:02:02 INFO: ionice priority: 5
  105: 2019-12-23 15:02:02 INFO: CT Name: sogo
  105: 2019-12-23 15:02:02 INFO: stopping vm
  105: 2019-12-23 15:02:06 INFO: creating archive '/mnt/pve/cephfs/dump/vzdump-lxc-105-2019_12_23-15_02_02.tar.lzo'
  105: 2019-12-23 15:03:03 INFO: Total bytes written: 3996938240 (3.8GiB, 68MiB/s)
  105: 2019-12-23 15:03:03 INFO: archive file size: 1.19GB
  105: 2019-12-23 15:03:03 INFO: VM_FNAM_DUP=vzdump-lxc-105-sogo
  105: 2019-12-23 15:03:03 INFO: ++ wc -l
  105: 2019-12-23 15:03:03 INFO: ++ ls -1 vzdump-lxc-105-sogo-2019_12_14-02_08_04.tar.lzo vzdump-lxc-105-sogo-2019_12_21-01_07_10.tar.lzo
vzdump-lxc-105-sogo-2019_12_23-11_41_33.tar.lzo vzdump-lxc-105-sogo-2019_12_23-15_02_02.tar.lzo
  105: 2019-12-23 15:03:03 INFO: + NUMFILES=4
  105: 2019-12-23 15:03:03 INFO: MAXFILES=11/2019see/fbc/bin/pve/backup.sh 2
  105: 2019-12-23 15:03:03 INFO: + echo MAXFILES=11/2019see/fbc/bin/pve/backup.sh 2
  105: 2019-12-23 15:03:03 INFO: + [[ 11/2019see/fbc/bin/pve/backup.sh
  105: 2019-12-23 15:03:03 INFO: 2 =~ ^-?[0-9]+$ ]]
  105: 2019-12-23 15:03:03 INFO: + '[' -e /nvme-ext4/dump ']'
  105: 2019-12-23 15:03:03 INFO: + rm -fv /nvme-ext4/dump/vzdump-lxc-105-sogo-2019_12_23-11_41_33.tar.lzo
  105: 2019-12-23 15:03:03 INFO: removed '/nvme-ext4/dump/vzdump-lxc-105-sogo-2019_12_23-11_41_33.tar.lzo'
  105: 2019-12-23 15:03:03 INFO: + cp -v vzdump-lxc-105-sogo-2019_12_23-15_02_02.tar.lzo /nvme-ext4/dump/
  105: 2019-12-23 15:03:04 INFO: 'vzdump-lxc-105-sogo-2019_12_23-15_02_02.tar.lzo' -> '/nvme-ext4/dump/vzdump-lxc-105-sogo-2019_12_23-15_02_02.tar.lzo'
  105: 2019-12-23 15:03:04 INFO: + '[' stop '!=' stop ']'
  105: 2019-12-23 15:03:04 INFO: + '[' backup-end == pre-stop ']'
  105: 2019-12-23 15:03:04 INFO: + '[' backup-end == backup-abort ']'
  105: 2019-12-23 15:03:04 INFO: restarting vm
  105: 2019-12-23 15:03:05 INFO: guest is online again after 63 seconds
  105: 2019-12-23 15:03:05 INFO: Finished Backup of VM 105 (00:01:03)
 
hi,

i did not test your script but i took a quick look.

it looks like you're changing the names of the backups. maybe that has to do something with your issue.

can you try to take backups without your custom script to test if maxfiles is being ignored?
 

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!