Backup failed with exit code 2

SAM_N

New Member
Nov 16, 2019
3
0
1
Hello together,

I tried to backup a new container on my Proxmox VE Version 5.4-4.
The container is running an "Ubuntu 18.04"-System.
During the process, I got this error message with the exit code 2:

Code:
INFO: starting new backup job: vzdump 100 --storage Backup --compress lzo --node pve --remove 0 --mode snapshot
INFO: Starting Backup of VM 100 (lxc)
INFO: status = running
INFO: CT Name: TEST
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: TEST
INFO: temporary directory is on NFS, disabling xattr and acl support, consider configuring a local tmpdir via /etc/vzdump.conf
INFO: starting first sync /proc/22388/root// to /mnt/pve/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tmp
INFO: Number of files: 27,882 (reg: 21,436, dir: 2,851, link: 3,564, special: 31)
INFO: Number of created files: 27,881 (reg: 21,436, dir: 2,850, link: 3,564, special: 31)
INFO: Number of deleted files: 0
INFO: Number of regular files transferred: 21,417
INFO: Total file size: 1,487,873,500 bytes
INFO: Total transferred file size: 1,350,324,594 bytes
INFO: Literal data: 1,350,325,223 bytes
INFO: Matched data: 0 bytes
INFO: File list size: 851,921
INFO: File list generation time: 0.001 seconds
INFO: File list transfer time: 0.000 seconds
INFO: Total bytes sent: 1,352,280,166
INFO: Total bytes received: 434,222
INFO: sent 1,352,280,166 bytes  received 434,222 bytes  13,197,213.54 bytes/sec
INFO: total size is 1,487,873,500  speedup is 1.10
INFO: first sync finished (102 seconds)
INFO: suspend vm
INFO: starting final sync /proc/22388/root// to /mnt/pve/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tmp
INFO: Number of files: 27,882 (reg: 21,436, dir: 2,851, link: 3,564, special: 31)
INFO: Number of created files: 0
INFO: Number of deleted files: 0
INFO: Number of regular files transferred: 5
INFO: Total file size: 1,487,890,513 bytes
INFO: Total transferred file size: 130,606,735 bytes
INFO: Literal data: 25,292 bytes
INFO: Matched data: 130,581,443 bytes
INFO: File list size: 65,535
INFO: File list generation time: 0.001 seconds
INFO: File list transfer time: 0.000 seconds
INFO: Total bytes sent: 800,761
INFO: Total bytes received: 120,264
INFO: sent 800,761 bytes  received 120,264 bytes  167,459.09 bytes/sec
INFO: total size is 1,487,890,513  speedup is 1,615.47
INFO: final sync finished (5 seconds)
INFO: resume vm
INFO: vm is online again after 6 seconds
INFO: creating archive '/mnt/pve/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tar.lzo'
INFO: tar: ./var/cache/apt/archives/partial: Cannot open: Permission denied
INFO: tar: ./var/lib/apt/lists/partial: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/mysql: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/performance_schema: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/TEST: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/aria_log.00000001: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/aria_log_control: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/ib_logfile0: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/ib_logfile1: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/ibdata1: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/multi-master.info: Cannot open: Permission denied
INFO: tar: ./var/lib/mysql/tc.log: Cannot open: Permission denied
INFO: tar: ./var/lib/php/sessions/sess_j2cumhm9mag81otvk3urmljdd9: Cannot open: Permission denied
INFO: tar: ./var/lib/postfix/master.lock: Cannot open: Permission denied
INFO: tar: ./var/lib/snmp/snmpd.conf: Cannot open: Permission denied
INFO: tar: ./var/log/mysql: Cannot open: Permission denied
INFO: tar: ./var/log/auth.log: Cannot open: Permission denied
INFO: tar: ./var/log/mail.log: Cannot open: Permission denied
INFO: tar: ./var/log/syslog: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/active: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/bounce: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/corrupt: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/defer: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/deferred: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/flush: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/hold: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/incoming: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/maildrop: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/private: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/public: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/saved: Cannot open: Permission denied
INFO: tar: ./var/spool/postfix/trace: Cannot open: Permission denied
INFO: tar: ./var/spool/rsyslog: Cannot open: Permission denied
INFO: Total bytes written: 1118330880 (1.1GiB, 32MiB/s)
INFO: tar: Exiting with failure status due to previous errors
ERROR: Backup of VM 100 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/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tmp' ./etc/vzdump/pct.conf '--directory=/mnt/pve/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tmp' --no-anchored '--exclude=lost+found' --anchored '--exclude=./tmp/?*' '--exclude=./var/tmp/?*' '--exclude=./var/run/?*.pid' . | lzop >/mnt/pve/Backup/dump/vzdump-lxc-100-2019_11_16-13_30_12.tar.dat' failed: exit code 2
INFO: Backup job finished with errors
TASK ERROR: job errors
I changed between a manual backup and a time backup, but the backup still failed.
Maybe someone of you can help me with this problem.

Best regards,

SAM_N
 
Last edited:

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
1,259
139
63
hi,

is the container privileged or unprivileged?
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
1,259
139
63
For unprivileged container You can use STOP mode
the backup mode has nothing to do with privileged/unprivileged. it depends on the underlying storage (if it supports snapshots or not)
 

timonych

Member
Aug 8, 2017
48
3
13
29
the backup mode has nothing to do with privileged/unprivileged. it depends on the underlying storage (if it supports snapshots or not)
NFS storage can consist of QCOW images
the backup mode has nothing to do with privileged/unprivileged. it depends on the underlying storage (if it supports snapshots or not)
But if I would backup VM with RAM Image and Backup storage is NFS storage - there is no error.
If I would backup Unprivelleged LXC to NFS Storage it will failed in Snapshot/Suspend mode and have success in Stop mode.
 

oguz

Proxmox Staff Member
Staff member
Nov 19, 2018
1,259
139
63
NFS storage can consist of QCOW images
yes, but containers use raw images on NFS

If I would backup Unprivelleged LXC to NFS Storage it will failed in Snapshot/Suspend mode and have success in Stop mode.
again, this doesn't have anything to do with privileged/unprivileged.
 

screenie

Active Member
Jul 21, 2009
157
4
38
I do have the same issue with an LXC container (unprivileged) on a local hw raid with LVM - backup destination is NFS.
Running version 6.1

Thanks,
screenie

hi,

is the container privileged or unprivileged?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!