all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [PVE-User] Vm Reboot + Start during backup
@ 2025-03-18  8:33 Eneko Lacunza via pve-user
  2025-03-18  8:41 ` Eneko Lacunza via pve-user
  0 siblings, 1 reply; 2+ messages in thread
From: Eneko Lacunza via pve-user @ 2025-03-18  8:33 UTC (permalink / raw)
  To: Proxmox VE user list; +Cc: Eneko Lacunza

[-- Attachment #1: Type: message/rfc822, Size: 7816 bytes --]

From: Eneko Lacunza <elacunza@binovo.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Vm Reboot + Start during backup
Date: Tue, 18 Mar 2025 09:33:38 +0100
Message-ID: <16888ca6-0bf2-4669-b026-bd0171420625@binovo.es>

Hi all,

Yesterday I configured a backup task in a recently updated PVE 8.3.5 .

Tonight's first run was mostly OK, but 5 of the 61 Windows VMs where 
rebooted + started for the backup.

VM disk storage is on ZFS mirror, NVMe disks.

Rebooted + Started VMs have each 1 snapshot, virtio disk and qemu agent.

There is a VM with virtio disk and qemu agent, but without snapshot. 
That VM was not rebooted + started.

Other VMs don't have snapshot nor qemu agent. Disk is ide.

Seems snapshot is related.

Is this the expected behaviour?

Thanks

proxmox-ve: 8.3.0 (running kernel: 6.8.12-8-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)
proxmox-kernel-helper: 8.1.1
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
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.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
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.2.0
libpve-network-perl: 0.10.1
libpve-rs-perl: 0.9.2
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.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.6
pve-cluster: 8.0.10
pve-container: 5.2.4
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-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.2.0-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1

Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project

Tel. +34 943 569 206 | https://www.binovo.es
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun

https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/



[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PVE-User] Vm Reboot + Start during backup
  2025-03-18  8:33 [PVE-User] Vm Reboot + Start during backup Eneko Lacunza via pve-user
@ 2025-03-18  8:41 ` Eneko Lacunza via pve-user
  0 siblings, 0 replies; 2+ messages in thread
From: Eneko Lacunza via pve-user @ 2025-03-18  8:41 UTC (permalink / raw)
  To: Proxmox VE user list; +Cc: Eneko Lacunza

[-- Attachment #1: Type: message/rfc822, Size: 6375 bytes --]

From: Eneko Lacunza <elacunza@binovo.es>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Vm Reboot + Start during backup
Date: Tue, 18 Mar 2025 09:41:49 +0100
Message-ID: <358e99d0-b327-4215-bfe2-546c6c8dede4@binovo.es>

Hi,

Forgot to mention that backup mode is snapshot.

Thanks

El 18/3/25 a las 9:33, Eneko Lacunza via pve-user escribió:
> Hi all,
>
> Yesterday I configured a backup task in a recently updated PVE 8.3.5 .
>
> Tonight's first run was mostly OK, but 5 of the 61 Windows VMs where 
> rebooted + started for the backup.
>
> VM disk storage is on ZFS mirror, NVMe disks.
>
> Rebooted + Started VMs have each 1 snapshot, virtio disk and qemu agent.
>
> There is a VM with virtio disk and qemu agent, but without snapshot. 
> That VM was not rebooted + started.
>
> Other VMs don't have snapshot nor qemu agent. Disk is ide.
>
> Seems snapshot is related.
>
> Is this the expected behaviour?
>
> Thanks 

Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project

Tel. +34 943 569 206 | https://www.binovo.es
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun

https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/



[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-03-18  8:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-03-18  8:33 [PVE-User] Vm Reboot + Start during backup Eneko Lacunza via pve-user
2025-03-18  8:41 ` Eneko Lacunza via pve-user

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal