[SOLVED] I am trying to run a scheduled backup for my VMs and it always fails with error:job error. I don't know what is wrong and I am also new to proxmox

[deb]

INFO: starting new backup job: vzdump 101 --mode snapshot --notification-mode auto --notes-template '{{guestname}}' --storage vmbkup --compress zstd --remove 0 --node pve
INFO: Starting Backup of VM 101 (lxc)
INFO: Backup started at 2025-01-17 06:30:51
INFO: status = running
INFO: CT Name: Ubuntu24-04docker
INFO: including mount point rootfs ('/') in backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-101-disk-0_vzdump" created.
INFO: creating vzdump archive '/mnt/pve/vmbkup/dump/vzdump-lxc-101-2025_01_17-06_30_51.tar.zst'
INFO: tar: /mnt/pve/vmbkup/dump/vzdump-lxc-101-2025_01_17-06_30_51.tmp: Cannot open: Permission denied
INFO: tar: Error is not recoverable: exiting now
INFO: cleanup temporary 'vzdump' snapshot
Logical volume "snap_vm-101-disk-0_vzdump" successfully removed.
ERROR: Backup of VM 101 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' --one-file-system '--warning=no-file-ignored' '--directory=/mnt/pve/vmbkup/dump/vzdump-lxc-101-2025_01_17-06_30_51.tmp' ./etc/vzdump/pct.conf ./etc/vzdump/pct.fw '--directory=/mnt/vzsnap0' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' ./ | zstd '--threads=1' >/mnt/pve/vmbkup/dump/vzdump-lxc-101-2025_01_17-06_30_51.tar.dat' failed: exit code 2
INFO: Failed at 2025-01-17 06:30:52
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[cheiss]

Hi,

INFO: tar: /mnt/pve/vmbkup/dump/vzdump-lxc-101-2025_01_17-06_30_51.tmp: Cannot open: Permission denied

as you can see from the log, it fails to open the backup target file.
What type is the vmbkup storage? This error most often happens with NFS and incorrect permissions.

Also, please provide the output of pveversion -v.

 

[gfngfn256]

Post output of the following:

cat /etc/pve/storage.cfg

pct config 101

Paste the output in the code editor on the formatting-bar in the reply box, by choosing the "</>" button & pasting there.

 

[deb]

Hi,


as you can see from the log, it fails to open the backup target file.
What type is the vmbkup storage? This error most often happens with NFS and incorrect permissions.

Also, please provide the output of

pveversion -v

.

a NFS storage XD
I went to my nas and made new user name guest for the container gave it access to the mount vmbkup and used NFS squash to map alluser to guest and it fixed it
I don't know if it a safe practice or not

here is the output for

pveversion -v

proxmox-ve: 8.3.0 (running kernel: 6.8.12-5-pve)
pve-manager: 8.3.2 (running version: 8.3.2/3e76eec21c4a14a7)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-6
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.3
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-2
pve-ha-manager: 4.0.6
pve-i18n: 3.3.2
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

 

[deb]

Post output of the following:

cat /etc/pve/storage.cfg

pct config 101

Paste the output in the code editor on the formatting-bar in the reply box, by choosing the "</>" button & pasting there.

here is the output

dir: local
        path /var/lib/vz
        content vztmpl,iso
        shared 0

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

nfs: proxmox
        export /Volume1/proxmox
        path /mnt/pve/proxmox
        server ""
        content images,rootdir
        prune-backups keep-all=1

nfs: vmbkup
        export /Volume1/vmbkup
        path /mnt/pve/vmbkup
        server ""
        content backup,vztmpl,iso
        prune-backups keep-all=1

arch: amd64
cores: 2
description: pass= pass%0A
features: nesting=1
hostname: Ubuntu24-04docker
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr="",ip=dhcp,ip6=dhcp,type=veth
ostype: ubuntu
rootfs: local-lvm:vm-101-disk-0,size=20G
swap: 512
unprivileged: 1

 

[gfngfn256]

As I thought it is NAS-based storage. I note you have solved this issue with your own procedure. I was going to suggest setting a local tmpdir in the /etc/vzdump.conf file as in the docs. This will cause the backup to temporarily be created locally (non-NFS) & only then be transferred to the backup storage (NFS). If you want you could still give this a try.