Proxmox default dumpdir setting ignored

[lineconnect]

Hi Folks,

i've a CIFS share and need that the proxmox backups are not stored under root. It needs to be in something like /proxmoxserver-xyz/dump.


I've changed the dumpdir in vzdump.conf but it seem's to be ignored

conf file:

# vzdump default settings

#tmpdir: DIR
dumpdir: proxmoxserver-xyz
#storage: ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#size: MB
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
#maxfiles: N
#script: FILENAME
#exclude-path: PATHLIST
#pigz: N

2021-07-21 21:19:09 INFO: Starting Backup of VM 107 (lxc)
2021-07-21 21:19:09 INFO: status = stopped
2021-07-21 21:19:09 INFO: backup mode: stop
2021-07-21 21:19:09 INFO: ionice priority: 7
2021-07-21 21:19:09 INFO: CT Name: wekan
2021-07-21 21:19:09 INFO: including mount point rootfs ('/') in backup
2021-07-21 21:19:09 INFO: creating vzdump archive '/mnt/pve/hetzner-storage-box/dump/vzdump-lxc-107-2021_07_21-21_19_09.tar.zst'
2021-07-21 21:19:44 INFO: Total bytes written: 5784012800 (5.4GiB, 161MiB/s)
2021-07-21 21:20:16 INFO: archive file size: 3.40GB
2021-07-21 21:20:17 INFO: Finished Backup of VM 107 (00:01:08)

Proxmox version:

proxmox-ve: 6.4-1 (running kernel: 5.4.124-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-4
pve-kernel-helper: 6.4-4
pve-kernel-5.4.124-1-pve: 5.4.124-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.12-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Have i made something wrong?

 

[oguz]

hi,

it works here. how are you running the backup? if you give the --storage option then it will be overridden, for example if i set dumpdir: /test

and then do a backup with vzdump

$ vzdump 11111
INFO: starting new backup job: vzdump 11111
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp466098_11111 for temporary files
INFO: Starting Backup of VM 11111 (lxc)
INFO: Backup started at 2021-07-22 14:30:28
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: CT11111
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/test/vzdump-lxc-11111-2021_07_22-14_30_28.tar'
INFO: Total bytes written: 735774720 (702MiB, 87MiB/s)
INFO: archive file size: 701MB
INFO: Finished Backup of VM 11111 (00:00:08)
INFO: Backup finished at 2021-07-22 14:30:36
INFO: Backup job finished successfully

but if i add --storage

$ vzdump 11111 --storage local
INFO: starting new backup job: vzdump 11111 --storage local
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp467767_11111 for temporary files
INFO: Starting Backup of VM 11111 (lxc)
INFO: Backup started at 2021-07-22 14:30:58
INFO: status = stopped
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: CT Name: CT11111
INFO: including mount point rootfs ('/') in backup
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-lxc-11111-2021_07_22-14_30_58.tar'
INFO: Total bytes written: 735774720 (702MiB, 123MiB/s)
INFO: archive file size: 701MB
INFO: prune older backups with retention: keep-last=5
INFO: pruned 0 backup(s)
INFO: Finished Backup of VM 11111 (00:00:05)
INFO: Backup finished at 2021-07-22 14:31:03
INFO: Backup job finished successfully

 

[lineconnect]

I'm doing the backup with the webUI function, to test that it will land on the correct place, when it get's done automatically.

Haven't test ist with the command line.

 

[oguz]

I'm doing the backup with the webUI function, to test that it will land on the correct place, when it get's done automatically.

when you do it on the GUI the storage option is set, so it will be overridden then (since the --storage flag is being set)

you could always create a storage for your backups and set that as the target

 

[lineconnect]

I'm using a CIFS storage as backup destination and i'm not in control of these share, so it's necessary for me to set the dump dir folder name.

Is there a option to edit some configs which will result in a custom dump location?

 

[oguz]

I'm using a CIFS storage as backup destination and i'm not in control of these share, so it's necessary for me to set the dump dir folder name.

how do you mean?

Is there a option to edit some configs which will result in a custom dump location?

hmm, dumpdir and storage are exclusive options so i think without hacky workarounds that can't work...

 

[lineconnect]

Sorry for the late answer.

how do you mean?

I've a rent CIFS storage which has a fixed share name and two proxmox instances running. Both should place their backups on that share and it would be good to have a folder structure where it's visible, which backup has been uploaded by which server.
So the share has the name '/backup' and each proxmox server should dump their backups in '/backup/proxmox-server0/dumps'

--
Lineconnect