The host system does not turn off the guest in the "stop" mode

S

Skrimer

Member
Oct 21, 2018
14
1
23
34
Hello!
I have been learning Proxmox for a year now, so I’m still a novice.)
Actually, the problem is in the title of the topic.
Proxmox without a subscription (for now) with the latest updates for today, guest - WinServer12.
Problem: after attempting to perform a backup on a schedule, it came to the mail "start failed: org.freedesktop.systemd1.UnitExists: Unit 117.scope already exists.".
After I discovered that in the "Stop" mode the guest system does not shut down, but is rebooted.
That is, when you manually start the backup, the following happens: the system starts to shut down, turns off, the backup process starts (“INFO: status: 0%”) and the system turns on. While writing a message, Proxmox performs a reservation in the "stop" mode, but the system is running.

vzdump 117 --storage local --mode stop --compress lzo --quiet 1 --mailnotification always --mailto


117: 2018-10-20 00:01:02 INFO: Starting Backup of VM 117 (qemu)
117: 2018-10-20 00:01:02 INFO: status = running
117: 2018-10-20 00:01:02 INFO: update VM 117: -lock backup
117: 2018-10-20 00:01:02 INFO: backup mode: stop
117: 2018-10-20 00:01:02 INFO: ionice priority: 7
117: 2018-10-20 00:01:02 INFO: VM Name: vvm-w2k12
117: 2018-10-20 00:01:02 INFO: include disk 'virtio0' 'local-zfs:vm-117-disk-2' 500G
117: 2018-10-20 00:01:02 INFO: include disk 'virtio1' 'local-zfs:vm-117-disk-0' 32G
117: 2018-10-20 00:01:02 INFO: stopping vm
117: 2018-10-20 00:01:11 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-117-2018_10_20-00_01_02.vma.lzo'
117: 2018-10-20 00:01:11 INFO: starting kvm to execute backup task
117: 2018-10-20 00:01:12 INFO: restarting vm
117: 2018-10-20 00:01:13 INFO: vm is online again after 11 seconds
117: 2018-10-20 00:01:13 ERROR: Backup of VM 117 failed - start failed: org.freedesktop.systemd1.UnitExists: Unit 117.scope already exists.

Thank!
 
Do you run latest version?

Please post the output of:

> pveversion -v
 
tom said:
Do you run latest version?

Please post the output of:

> pveversion -v
Click to expand...

proxmox-ve: 5.2-2 (running kernel: 4.15.18-7-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-28
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1
 
Last edited:
Goodmorning everyone,
I have the same problem too.
unfortunately, if the backup tool is not solved (unreliable) it affects the whole infrastructure of my client. No solution? below the resent of pveversion -v
Thank you all.

Post Scriptum:
manual backup works perfectly.

pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-7-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-26
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-28
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1
 
augusto baldi said:
Goodmorning everyone,
I have the same problem too.
unfortunately, if the backup tool is not solved (unreliable) it affects the whole infrastructure of my client. No solution? below the resent of pveversion -v
Thank you all.

Post Scriptum:
manual backup works perfectly.

pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-7-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-26
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-28
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1
Click to expand...

A week ago, my automatic backup worked fine.

vzdump 117 --quiet 1 --storage local --mailnotification always --compress lzo --mailto ####### --mode stop


117: 2018-10-13 00:01:01 INFO: Starting Backup of VM 117 (qemu)
117: 2018-10-13 00:01:01 INFO: status = running
117: 2018-10-13 00:01:01 INFO: update VM 117: -lock backup
117: 2018-10-13 00:01:01 INFO: backup mode: stop
117: 2018-10-13 00:01:01 INFO: ionice priority: 7
117: 2018-10-13 00:01:01 INFO: VM Name: vvm-w2k12
117: 2018-10-13 00:01:01 INFO: include disk 'virtio0' 'local-zfs:vm-117-disk-2' 500G
117: 2018-10-13 00:01:02 INFO: include disk 'virtio1' 'local-zfs:vm-117-disk-0' 32G
117: 2018-10-13 00:01:02 INFO: stopping vm
117: 2018-10-13 00:01:11 INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-117-2018_10_13-00_01_01.vma.lzo'
117: 2018-10-13 00:01:11 INFO: starting kvm to execute backup task
117: 2018-10-13 00:01:12 INFO: started backup task '0660173d-a82d-4919-a714-6f9688a3a681'
117: 2018-10-13 00:01:12 INFO: resume VM
117: 2018-10-13 00:01:15 INFO: status: 0% (333316096/571230650368), sparse 0% (21798912), duration 3, read/write 111/103 MB/s
117: 2018-10-13 00:02:39 INFO: status: 1% (5736693760/571230650368), sparse 0% (169877504), duration 87, read/write 64/62 MB/s
117: 2018-10-13 00:04:03 INFO: status: 2% (11513495552/571230650368), sparse 0% (307638272), duration 171, read/write 68/67 MB/s
117: 2018-10-13 00:05:25 INFO: status: 3% (17234132992/571230650368), sparse 0% (453586944), duration 253, read/write 69/67 MB/s
117: 2018-10-13 00:06:34 INFO: status: 4% (22849454080/571230650368), sparse 0% (509878272), duration 322, read/write 81/80 MB/s
117: 2018-10-13 00:08:02 INFO: status: 5% (28585623552/571230650368), sparse 0% (586461184), duration 410, read/write 65/64 MB/s
117: 2018-10-13 00:09:27 INFO: status: 6% (34349449216/571230650368), sparse 0% (676921344), duration 495, read/write 67/66 MB/s
117: 2018-10-13 00:10:44 INFO: status: 7% (39992557568/571230650368), sparse 0% (725970944), duration 572, read/write 73/72 MB/s
117: 2018-10-13 00:11:46 INFO: status: 8% (45749895168/571230650368), sparse 0% (746688512), duration 634, read/write 92/92 MB/s
117: 2018-10-13 00:13:09 INFO: status: 9% (51466731520/571230650368), sparse 0% (780357632), duration 717, read/write 68/68 MB/s
117: 2018-10-13 00:14:36 INFO: status: 10% (57155256320/571230650368), sparse 0% (817098752), duration 804, read/write 65/64 MB/s
117: 2018-10-13 00:15:53 INFO: status: 11% (62853218304/571230650368), sparse 0% (846344192), duration 881, read/write 73/73 MB/s
117: 2018-10-13 00:17:14 INFO: status: 12% (68561928192/571230650368), sparse 0% (900784128), duration 962, read/write 70/69 MB/s
117: 2018-10-13 00:18:23 INFO: status: 13% (74353082368/571230650368), sparse 0% (935358464), duration 1031, read/write 83/83 MB/s
117: 2018-10-13 00:19:44 INFO: status: 14% (80004907008/571230650368), sparse 0% (962678784), duration 1112, read/write 69/69 MB/s
117: 2018-10-13 00:21:02 INFO: status: 15% (85768798208/571230650368), sparse 0% (1008934912), duration 1190, read/write 73/73 MB/s
117: 2018-10-13 00:22:15 INFO: status: 16% (91404566528/571230650368), sparse 0% (1078939648), duration 1263, read/write 77/76 MB/s
117: 2018-10-13 00:23:24 INFO: status: 17% (97172717568/571230650368), sparse 0% (1119072256), duration 1332, read/write 83/83 MB/s
117: 2018-10-13 00:24:16 INFO: status: 18% (102872514560/571230650368), sparse 0% (1133645824), duration 1384, read/write 109/109 MB/s
117: 2018-10-13 00:25:51 INFO: status: 19% (108618711040/571230650368), sparse 0% (1198821376), duration 1479, read/write 60/59 MB/s
117: 2018-10-13 00:27:19 INFO: status: 20% (114281218048/571230650368), sparse 0% (1292386304), duration 1567, read/write 64/63 MB/s
117: 2018-10-13 00:28:39 INFO: status: 21% (120030756864/571230650368), sparse 0% (1354825728), duration 1647, read/write 71/71 MB/s
117: 2018-10-13 00:29:38 INFO: status: 22% (125945577472/571230650368), sparse 0% (1515450368), duration 1706, read/write 100/97 MB/s
117: 2018-10-13 00:30:06 INFO: status: 23% (131478847488/571230650368), sparse 0% (1636364288), duration 1734, read/write 197/193 MB/s
117: 2018-10-13 00:30:51 INFO: status: 24% (137186115584/571230650368), sparse 0% (1709703168), duration 1779, read/write 126/125 MB/s
117: 2018-10-13 00:31:40 INFO: status: 25% (142895480832/571230650368), sparse 0% (1740378112), duration 1828, read/write 116/115 MB/s
117: 2018-10-13 00:32:20 INFO: status: 26% (148735262720/571230650368), sparse 0% (1753071616), duration 1868, read/write 145/145 MB/s
117: 2018-10-13 00:32:58 INFO: status: 27% (154301366272/571230650368), sparse 0% (1765273600), duration 1906, read/write 146/146 MB/s
117: 2018-10-13 00:33:37 INFO: status: 28% (160005881856/571230650368), sparse 0% (1784209408), duration 1945, read/write 146/145 MB/s
117: 2018-10-13 00:34:13 INFO: status: 29% (165663932416/571230650368), sparse 0% (1804718080), duration 1981, read/write 157/156 MB/s
117: 2018-10-13 00:35:02 INFO: status: 30% (171437326336/571230650368), sparse 0% (1855651840), duration 2030, read/write 117/116 MB/s
117: 2018-10-13 00:35:49 INFO: status: 31% (177151016960/571230650368), sparse 0% (1867804672), duration 2077, read/write 121/121 MB/s
117: 2018-10-13 00:36:36 INFO: status: 32% (182836527104/571230650368), sparse 0% (1874137088), duration 2124, read/write 120/120 MB/s
117: 2018-10-13 00:37:23 INFO: status: 33% (188669231104/571230650368), sparse 0% (1876275200), duration 2171, read/write 124/124 MB/s
117: 2018-10-13 00:38:12 INFO: status: 34% (194304016384/571230650368), sparse 0% (1888620544), duration 2220, read/write 114/114 MB/s
117: 2018-10-13 00:38:55 INFO: status: 35% (199977926656/571230650368), sparse 0% (1890480128), duration 2263, read/write 131/131 MB/s
117: 2018-10-13 00:39:37 INFO: status: 36% (205689520128/571230650368), sparse 0% (1892843520), duration 2305, read/write 135/135 MB/s
117: 2018-10-13 00:40:24 INFO: status: 37% (211433095168/571230650368), sparse 0% (1898528768), duration 2352, read/write 122/122 MB/s
117: 2018-10-13 00:41:09 INFO: status: 38% (217099403264/571230650368), sparse 0% (1902272512), duration 2397, read/write 125/125 MB/s
117: 2018-10-13 00:41:55 INFO: status: 39% (222890295296/571230650368), sparse 0% (1906581504), duration 2443, read/write 125/125 MB/s
117: 2018-10-13 00:42:38 INFO: status: 40% (228564533248/571230650368), sparse 0% (1911029760), duration 2486, read/write 131/131 MB/s
117: 2018-10-13 00:43:23 INFO: status: 41% (234247159808/571230650368), sparse 0% (1915727872), duration 2531, read/write 126/126 MB/s
117: 2018-10-13 00:44:07 INFO: status: 42% (239988834304/571230650368), sparse 0% (1920032768), duration 2575, read/write 130/130 MB/s
117: 2018-10-13 00:44:43 INFO: status: 43% (245690859520/571230650368), sparse 0% (1920946176), duration 2611, read/write 158/158 MB/s
117: 2018-10-13 00:45:25 INFO: status: 44% (251345633280/571230650368), sparse 0% (1930629120), duration 2653, read/write 134/134 MB/s
117: 2018-10-13 00:46:09 INFO: status: 45% (257097465856/571230650368), sparse 0% (1948774400), duration 2697, read/write 130/130 MB/s
117: 2018-10-13 00:47:08 INFO: status: 46% (262829047808/571230650368), sparse 0% (1961132032), duration 2756, read/write 97/96 MB/s
117: 2018-10-13 00:48:03 INFO: status: 47% (268505317376/571230650368), sparse 0% (2002980864), duration 2811, read/write 103/102 MB/s
117: 2018-10-13 00:49:00 INFO: status: 48% (274250203136/571230650368), sparse 0% (2018066432), duration 2868, read/write 100/100 MB/s
117: 2018-10-13 00:50:04 INFO: status: 49% (279935516672/571230650368), sparse 0% (2069168128), duration 2932, read/write 88/88 MB/s
117: 2018-10-13 00:51:08 INFO: status: 50% (285616570368/571230650368), sparse 0% (2094518272), duration 2996, read/write 88/88 MB/s
117: 2018-10-13 00:52:16 INFO: status: 51% (291373121536/571230650368), sparse 0% (2125885440), duration 3064, read/write 84/84 MB/s
117: 2018-10-13 00:53:17 INFO: status: 52% (297045983232/571230650368), sparse 0% (2147663872), duration 3125, read/write 92/92 MB/s
117: 2018-10-13 00:54:08 INFO: status: 53% (302790737920/571230650368), sparse 0% (2158940160), duration 3176, read/write 112/112 MB/s
117: 2018-10-13 00:55:00 INFO: status: 54% (308520353792/571230650368), sparse 0% (2176573440), duration 3228, read/write 110/109 MB/s
117: 2018-10-13 00:55:53 INFO: status: 55% (314210910208/571230650368), sparse 0% (2189299712), duration 3281, read/write 107/107 MB/s
117: 2018-10-13 00:56:48 INFO: status: 56% (319961432064/571230650368), sparse 0% (2203643904), duration 3336, read/write 104/104 MB/s
117: 2018-10-13 00:57:42 INFO: status: 57% (325639733248/571230650368), sparse 0% (2217115648), duration 3390, read/write 105/104 MB/s
117: 2018-10-13 00:58:29 INFO: status: 58% (331314233344/571230650368), sparse 0% (2225696768), duration 3437, read/write 120/120 MB/s
117: 2018-10-13 00:59:25 INFO: status: 59% (337093918720/571230650368), sparse 0% (2227286016), duration 3493, read/write 103/103 MB/s
117: 2018-10-13 01:00:05 INFO: status: 60% (342809968640/571230650368), sparse 0% (2451800064), duration 3533, read/write 142/137 MB/s
117: 2018-10-13 01:01:01 INFO: status: 61% (348540764160/571230650368), sparse 0% (2467500032), duration 3589, read/write 102/102 MB/s
117: 2018-10-13 01:02:01 INFO: status: 62% (354174304256/571230650368), sparse 0% (2484133888), duration 3649, read/write 93/93 MB/s
117: 2018-10-13 01:03:02 INFO: status: 63% (359890812928/571230650368), sparse 0% (2500866048), duration 3710, read/write 93/93 MB/s
117: 2018-10-13 01:03:59 INFO: status: 64% (365642579968/571230650368), sparse 0% (2527268864), duration 3767, read/write 100/100 MB/s
117: 2018-10-13 01:05:00 INFO: status: 65% (371377569792/571230650368), sparse 0% (2558251008), duration 3828, read/write 94/93 MB/s
117: 2018-10-13 01:05:57 INFO: status: 66% (377040273408/571230650368), sparse 0% (2578321408), duration 3885, read/write 99/98 MB/s
117: 2018-10-13 01:06:53 INFO: status: 67% (382794465280/571230650368), sparse 0% (2589290496), duration 3941, read/write 102/102 MB/s
117: 2018-10-13 01:07:48 INFO: status: 68% (388522049536/571230650368), sparse 0% (2611126272), duration 3996, read/write 104/103 MB/s
117: 2018-10-13 01:08:30 INFO: status: 69% (394238296064/571230650368), sparse 0% (2611527680), duration 4038, read/write 136/136 MB/s
117: 2018-10-13 01:08:57 INFO: status: 70% (400063725568/571230650368), sparse 0% (2611531776), duration 4065, read/write 215/215 MB/s
117: 2018-10-13 01:09:25 INFO: status: 71% (405579890688/571230650368), sparse 0% (2611535872), duration 4093, read/write 197/197 MB/s
117: 2018-10-13 01:09:54 INFO: status: 72% (411335655424/571230650368), sparse 0% (2611552256), duration 4122, read/write 198/198 MB/s
117: 2018-10-13 01:10:45 INFO: status: 73% (417085784064/571230650368), sparse 0% (2631569408), duration 4173, read/write 112/112 MB/s
117: 2018-10-13 01:11:33 INFO: status: 74% (422788923392/571230650368), sparse 0% (2631606272), duration 4221, read/write 118/118 MB/s
117: 2018-10-13 01:12:19 INFO: status: 75% (428616908800/571230650368), sparse 0% (3176747008), duration 4267, read/write 126/114 MB/s
117: 2018-10-13 01:12:30 INFO: status: 76% (434511413248/571230650368), sparse 1% (8340750336), duration 4278, read/write 535/66 MB/s
117: 2018-10-13 01:12:35 INFO: status: 77% (440651612160/571230650368), sparse 2% (14480949248), duration 4283, read/write 1228/0 MB/s
117: 2018-10-13 01:12:39 INFO: status: 78% (445589749760/571230650368), sparse 3% (19419086848), duration 4287, read/write 1234/0 MB/s
117: 2018-10-13 01:12:44 INFO: status: 79% (451681910784/571230650368), sparse 4% (25511247872), duration 4292, read/write 1218/0 MB/s
117: 2018-10-13 01:12:49 INFO: status: 80% (457751527424/571230650368), sparse 5% (31580864512), duration 4297, read/write 1213/0 MB/s
117: 2018-10-13 01:12:53 INFO: status: 81% (462733639680/571230650368), sparse 6% (36562976768), duration 4301, read/write 1245/0 MB/s
117: 2018-10-13 01:12:58 INFO: status: 82% (468968275968/571230650368), sparse 7% (42797613056), duration 4306, read/write 1246/0 MB/s
117: 2018-10-13 01:13:03 INFO: status: 83% (475151073280/571230650368), sparse 8% (48980410368), duration 4311, read/write 1236/0 MB/s
117: 2018-10-13 01:13:07 INFO: status: 84% (480124207104/571230650368), sparse 9% (53953544192), duration 4315, read/write 1243/0 MB/s
117: 2018-10-13 01:13:12 INFO: status: 85% (486329810944/571230650368), sparse 10% (60159148032), duration 4320, read/write 1241/0 MB/s
117: 2018-10-13 01:13:16 INFO: status: 86% (491304058880/571230650368), sparse 11% (65133395968), duration 4324, read/write 1243/0 MB/s
117: 2018-10-13 01:13:21 INFO: status: 87% (497521786880/571230650368), sparse 12% (71351123968), duration 4329, read/write 1243/0 MB/s
117: 2018-10-13 01:13:26 INFO: status: 88% (503637737472/571230650368), sparse 13% (77467074560), duration 4334, read/write 1223/0 MB/s
117: 2018-10-13 01:13:30 INFO: status: 89% (508563881984/571230650368), sparse 14% (82393219072), duration 4338, read/write 1231/0 MB/s
117: 2018-10-13 01:13:35 INFO: status: 90% (514714173440/571230650368), sparse 15% (88543510528), duration 4343, read/write 1230/0 MB/s
117: 2018-10-13 01:13:40 INFO: status: 91% (520913616896/571230650368), sparse 16% (94742953984), duration 4348, read/write 1239/0 MB/s
117: 2018-10-13 01:13:44 INFO: status: 92% (526104920064/571230650368), sparse 17% (99934253056), duration 4352, read/write 1297/0 MB/s
117: 2018-10-13 01:13:48 INFO: status: 93% (531676004352/571230650368), sparse 18% (105505337344), duration 4356, read/write 1392/0 MB/s
117: 2018-10-13 01:13:54 INFO: status: 94% (537765675008/571230650368), sparse 19% (111364005888), duration 4362, read/write 1014/38 MB/s
117: 2018-10-13 01:13:58 INFO: status: 95% (543485329408/571230650368), sparse 20% (117083660288), duration 4366, read/write 1429/0 MB/s
117: 2018-10-13 01:14:02 INFO: status: 96% (548779982848/571230650368), sparse 21% (122378313728), duration 4370, read/write 1323/0 MB/s
117: 2018-10-13 01:14:07 INFO: status: 97% (555136516096/571230650368), sparse 22% (128734846976), duration 4375, read/write 1271/0 MB/s
117: 2018-10-13 01:14:11 INFO: status: 98% (560186589184/571230650368), sparse 23% (133784920064), duration 4379, read/write 1262/0 MB/s
117: 2018-10-13 01:14:15 INFO: status: 99% (565584527360/571230650368), sparse 24% (139182858240), duration 4383, read/write 1349/0 MB/s
117: 2018-10-13 01:14:19 INFO: status: 100% (571230650368/571230650368), sparse 25% (144828973056), duration 4387, read/write 1411/0 MB/s
117: 2018-10-13 01:14:19 INFO: transferred 571230 MB in 4387 seconds (130 MB/s)
117: 2018-10-13 01:14:19 INFO: archive file size: 304.59GB
117: 2018-10-13 01:14:21 INFO: vm is online again after 4399 seconds
117: 2018-10-13 01:14:21 INFO: Finished Backup of VM 117 (01:13:20)
 
Я подниму тему:
Он обратил внимание на ручное резервирование. Почему «INFO: возобновить VM» перед резервным копированием?
Мне кажется, из-за этого и возникла проблема.

[SPOILER = "Процесс бронирования"]
INFO: запуск новой резервной работы: vzdump 117 - остановка режима --compress lzo --node PVE - локальный локальный --remove 0
INFO: запуск резервного копирования VM 117 (qemu)
INFO: статус = работает
INFO: обновление VM 117: резервное копирование
INFO: режим резервного копирования: остановка
INFO: приоритет ионизации: 7
INFO: Имя VM: vvm-w2k12
INFO: включить диск 'virtio0' 'local-zfs: vm-117-disk-2' 500G
INFO: включить диск 'virtio1' 'local-zfs: vm-117-disk-0' 32G
INFO: остановка vm
INFO: создание архива '/var/lib/vz/dump/vzdump-qemu-117-2018_10_28-14_34_42.vma.lzo'
INFO: запуск kvm для выполнения задачи резервного копирования
INFO: начата задача резервного копирования '1507eacb-6eb5-4c3c-88af-5a5d919314ff'
INFO: возобновление VM
INFO: статус: 0% (314048512/571230650368), разреженный 0% (21790720), длительность 3, чтение / запись 104/97 МБ / с
........
[/СПОЙЛЕР]

Поблагодарить!
 
I will raise the topic:
He paid attention with manual reservation. Why is "INFO: resume VM" before backing up?
It seems to me because of this and the above problem appears.

INFO: starting new backup job: vzdump 117 --mode stop --compress lzo --node PVE --storage local --remove 0
INFO: Starting Backup of VM 117 (qemu)
INFO: status = running
INFO: update VM 117: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: vvm-w2k12
INFO: include disk 'virtio0' 'local-zfs:vm-117-disk-2' 500G
INFO: include disk 'virtio1' 'local-zfs:vm-117-disk-0' 32G
INFO: stopping vm
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-117-2018_10_28-14_34_42.vma.lzo'
INFO: starting kvm to execute backup task
INFO: started backup task '1507eacb-6eb5-4c3c-88af-5a5d919314ff'
INFO: resume VM
INFO: status: 0% (314048512/571230650368), sparse 0% (21790720), duration 3, read/write 104/97 MB/s
........................

Thank!
 
the backup of qemu vms works with a snapshot semantic,
if a write comes from the guest, the process backs it up first and blocks the guest write until that block is backed up

the 3 modes (stop,suspend,snapshot) are just to get the file system/disk in a consistent state via different methods
 
dcsapak said:
the backup of qemu vms works with a snapshot semantic,
if a write comes from the guest, the process backs it up first and blocks the guest write until that block is backed up

the 3 modes (stop,suspend,snapshot) are just to get the file system/disk in a consistent state via different methods
Click to expand...
Hello!
I do not quite understand what you wrote.
The problem is that the backup starts in the STOP mode, but ends with an error specified in the first message of the topic. For this reason, you have to make reservations manually, which is not convenient, to say the least.
 
INFO: starting new backup job: vzdump 117 --compress gzip --node PVE --mode stop --remove 0 --storage local
INFO: Starting Backup of VM 117 (qemu)
INFO: status = running
INFO: update VM 117: -lock backup
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: vvm-w2k12
INFO: include disk 'virtio0' 'local-zfs:vm-117-disk-2' 500G
INFO: include disk 'virtio1' 'local-zfs:vm-117-disk-0' 32G
INFO: stopping vm
INFO: creating archive '/var/lib/vz/dump/vzdump-qemu-117-2018_11_27-18_04_26.vma.gz'
INFO: starting kvm to execute backup task
INFO: started backup task '3c61d2ce-dc50-4e4e-a9b2-d692c1ba4358'
INFO: resume VM
INFO: status: 0% (95027200/571230650368), sparse 0% (21782528), duration 3, read/write 31/24 MB/s

Why does the VM resume operation when the backup is running in STOP mode?
 
Skrimer said:
Why does the VM resume operation when the backup is running in STOP mode?
Click to expand...
because qemu does a backup with snapshot semantics

before the vm writes, we write the corresponding block to the backup and let the vm then continue the write
 
dcsapak said:
because qemu does a backup with snapshot semantics

before the vm writes, we write the corresponding block to the backup and let the vm then continue the write
Click to expand...
Thank!
But I still do backups manually due to a problem from the first message.
Sorry, I probably have to change the hypervisor.
Found a branch with the same problem, too, without a specific solution.

https://forum.proxmox.com/threads/stop-vm-for-backup.35596/
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back