Backup schlägt fehl

Jul 22, 2019
10
1
6
33
Hallo zusammen,

ein Backup Job ist fehlgeschlagen und meldet folgendes:

Code:
VMID    NAME    STATUS    TIME    SIZE    FILENAME
100    passbolt    FAILED    00:10:05    got timeout
126    ubnt    FAILED    00:10:05    got timeout
...
...
...
TOTAL    01:40:53    0KB




Code:
Detailed backup logs:

vzdump 100 120 121 122 123 128 126 110 119 124 125 127 129 130 131 132 134 137 135 136 106 138 140 141 139 142 143 144 145 146 147 148 149 150 --mailnotification always --storage backups --mailto xxxxx --compress gzip --mode snapshot --quiet 1


100: 2019-11-27 20:00:02 INFO: Starting Backup of VM 100 (qemu)
100: 2019-11-27 20:00:02 INFO: status = running
100: 2019-11-27 20:00:03 INFO: update VM 100: -lock backup
100: 2019-11-27 20:00:03 INFO: VM Name: passbolt
100: 2019-11-27 20:00:03 INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 32G
100: 2019-11-27 20:00:03 INFO: backup mode: snapshot
100: 2019-11-27 20:00:03 INFO: ionice priority: 7
100: 2019-11-27 20:00:03 INFO: creating archive '/mnt/pve/backups/dump/vzdump-qemu-100-2019_11_27-20_00_02.vma.gz'
100: 2019-11-27 20:00:06 ERROR: got timeout
100: 2019-11-27 20:00:06 INFO: aborting backup job
100: 2019-11-27 20:10:06 ERROR: VM 100 qmp command 'backup-cancel' failed - got timeout
100: 2019-11-27 20:10:07 ERROR: Backup of VM 100 failed - got timeout

...
...

Was kann das für ursachen haben? Auf anderen Proxmox Knoten funktioniert alles einwandfrei.
 
bitte mal `pveversion -v` posten (und sicherstellen, dass die letzten updates installiert sind)
 
Hi Stoiko,

Code:
root@pve-05:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-11 (running version: 6.0-11/2140ef37)
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-2-pve: 5.0.21-7
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-7
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-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.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

Wenn ich das Backup manuell starten will erhalte ich direkt folgendes:

Code:
()
INFO: starting new backup job: vzdump 100 --compress lzo --node pve-05 --remove 0 --mode snapshot --storage backups
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2019-11-28 12:49:39
INFO: status = running
INFO: update VM 100: -lock backup
INFO: VM Name: passbolt
INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 32G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/backups/dump/vzdump-qemu-100-2019_11_28-12_49_39.vma.lzo'
ERROR: got timeout
INFO: aborting backup job
 

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!