Backup scheduler stop every day the VM

ok tried again from scheduled and ran the back up and it stuck as well

Code: 
INFO: starting new backup job: vzdump 104 --mailnotification always --all 0 --compress zstd --storage backup_drive --prune-backups 'keep-daily=1,keep-last=2,keep-weekly=1' --mode snapshot --node proxmox --mailto blackhole@gmail.com
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2022-02-02 07:47:19
INFO: status = running
INFO: VM Name: AlmaLinux
INFO: include disk 'scsi0' 'local-lvm:vm-104-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/backup_drive/dump/vzdump-qemu-104-2022_02_02-07_47_19.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command

7 mins so far, I will let it run and see what errors come up again, it might be 1 hour before it times out of freeze and thaw

sorry but thanks for helping

Spiro
 
Code: 
Securetmp enables /dev/loop mounts

You'll need to disable it if you want to run snapshots/backups with CloudLinux

https://support.cpanel.net/hc/en-us/articles/360058525333-How-to-disable-scripts-securetmp

This is what CloudLinux sent me

Hello,

The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening:

When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:
1) freeze loopback fs
---> send async reqs to loopback thread
2) freeze main fs
3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash.

I'm afraid we have no further recommendations at this point.

Thank you.
https://forum.proxmox.com/threads/e...fsfreeze-thaw-failed-got-timeout.68082/page-2

not sure if this helps to find the cause. I do not have cloudlinux, but AlmaLinux 8.5 with cPanel which they made in the first place
 
Spirog said:
7 mins so far, I will let it run and see what errors come up again, it might be 1 hour before it times out of freeze and thaw
Click to expand...
it's likely a guest-agent issue (since that's the component that sends the freeze/thaw commands to the VM).
as mentioned freeze/thaw can take a bit of time, especially if your storage is slow...

also i noticed you haven't posted your VM configuration, might be relevant at this point (qm config VMID, change VMID to yours)

what kind of storage are you using?
 
oguz said:
also i noticed you haven't posted your VM configuration, might be relevant at this point (qm config VMID, change VMID to yours)
Click to expand...
Code: 
agent: 1
boot: order=scsi0;ide2;net0
cores: 50
ide2: local:iso/AlmaLinux-8.5-x86_64-minimal.iso,media=cdrom
memory: 92160
meta: creation-qemu=6.1.0,ctime=1643453974
name: AlmaLinux
net0: virtio=B6:0C:91:75:75:D3,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-104-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=96a1e770-46b1-463b-9eb1-ba5d0abfd6b7
sockets: 1
vmgenid: e6f12321-0cd9-4117-bb08-99900aa2ae67

oguz said:
what kind of storage are you using?
Click to expand...

backup is 1TB HHD and main drive is 2x 1TB SSD in Raid
not sure what model or brad names?

Thanks
Spiro
 
oguz said:
freeze/thaw can take a bit of time, especially if your storage is slow..
Click to expand...
but for some reason after making the change in that file you suggested, and then trying it from the scheduler side, it was only 6 minutes and it finished the whole backup. but then when I tried with manual backup it started doing the same thing again freeze and times out thaw and times out then finally runs the backup, but the whole time my websites are down :(

@oguz did you get a change to read this other guys post here > https://forum.proxmox.com/threads/e...w-failed-got-timeout.68082/page-2#post-424844

- seems related to my issue, just not sure what issues I might have if I disable securetmp in cPanel ? and if I do not sure how to re-enable it ?


thanks again
Spiro
 
Spirog said:
just not sure what issues I might have if I disable securetmp in cPanel ? and if I do not sure how to re-enable it ?
Click to expand...
you could make a snapshot and try out... if it causes problems just revert ;)

Spirog said:
backup is 1TB HHD and main drive is 2x 1TB SSD in Raid
not sure what model or brad names?
Click to expand...
you can check with fdisk -l 2>/dev/null | grep -i model, but HDD might be on the slower side
 
Last edited:
  • Like
Reactions: Spirog
also, do you really have 50 cores and that much RAM available for the VM? aren't the other guests using some as well?
 
oguz said:
you could make a snapshot and try out... if it causes problems just revert ;)
Click to expand...
ok doing this now,

how to solve this errors?
Code: 
WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "vm-104-state-snapshot2222" created.
  WARNING: Sum of all thin volume sizes (1.15 TiB) exceeds the size of thin pool pve/data and the size of whole volume group (<930.50 GiB).
saving VM state and RAM using storage 'local-lvm'

or do not worry about this ?
 
oguz said:
nothing to worry about.
the short explanation: with LVM-thin storage you can provision more storage than you physically have (and add more physical disks later on when you need). this is possible because of "thin-provisioning" [0]


okay :)

[0]: https://pve.proxmox.com/wiki/Storage#_thin_provisioning
Click to expand...
well i did exactly that > Disabled /script/securetmp in cPanel
Following this guide
Code: 
https://support.cpanel.net/hc/en-us/articles/360058525333-How-to-disable-scripts-securetmp

and so far I tested 3 times and it works, will test again 3-4 times and later in a few hours, I will turn off VM then Turn back on and test Backups again in Snapshot mode,
I did so far 2 VM backup manually and also 1 manually from scheduled backup section. all took about 6 mins to finish never got stuck on freeze

later I will also set scheduled backup for 10 mins and let it backup with schedule and see if it stays working.

seems this might be the issue /script/securetmp needs to be disabled.. it was enabled on my cPanel VM with AlmaLinux 8.5
now I disable it and backups seems to be working
Also I think I should revert back the diff file i made changes to? or should I leave it alone ?


This might be the temp fix until you guys can figure out if you can get it working with securetmp enabled.
or we just need a disclaimer to turn it off in order to do backups using snapshot mode if we have issues freezing or cPanel users

I will report more in a few hours, I need to sleep as well :) thanks so much for Helping.

I do Appreciate you !!!

Kind Regards,
Spiro
 
@oguz it seesm to have solved this problem its working.. I tested after disabling
Spirog said:
Disabled /script/securetmp in cPanel
Following this guide
Code: 
https://support.cpanel.net/hc/en-us/articles/360058525333-How-to-disable-scripts-securetmp
Click to expand...
and then I did 3 one from VM backup section and another from schedule section and also a new one I setup scheduled to run at 10:17am and it ran and all finished in about 6-7 mins
also I rebooted and stopped and started VM just to check again and it still works
so this is the issue, not sure if you guys can get itto work somehow with /script/securetmp active? or if it will always need to get disabled in order to not have issues with Qemu Guest Agent for Snapshot backups?


here is the last backup working perfect now from all areas

Code: 
INFO: starting new backup job: vzdump 104 --mailto **@gmail.com --mode snapshot --mailnotification always --quiet 1 --storage backup_drive --compress zstd
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2022-02-02 10:17:01
INFO: status = running
INFO: VM Name: AlmaLinux
INFO: include disk 'scsi0' 'local-lvm:vm-104-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating vzdump archive '/mnt/backup_drive/dump/vzdump-qemu-104-2022_02_02-10_17_01.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '0f963042-995c-4962-8391-86df3a1645f1'
INFO: resuming VM again
INFO:   0% (2.9 GiB of 500.0 GiB) in 3s, read: 995.1 MiB/s, write: 83.5 MiB/s
INFO:   1% (5.3 GiB of 500.0 GiB) in 6s, read: 817.4 MiB/s, write: 105.0 MiB/s
INFO:   2% (11.7 GiB of 500.0 GiB) in 13s, read: 932.3 MiB/s, write: 85.7 MiB/s
INFO:   3% (18.2 GiB of 500.0 GiB) in 16s, read: 2.2 GiB/s, write: 0 B/s
INFO:   5% (27.0 GiB of 500.0 GiB) in 19s, read: 2.9 GiB/s, write: 0 B/s
INFO:   6% (34.0 GiB of 500.0 GiB) in 22s, read: 2.3 GiB/s, write: 0 B/s
INFO:   8% (41.0 GiB of 500.0 GiB) in 25s, read: 2.3 GiB/s, write: 2.0 MiB/s
INFO:   9% (48.1 GiB of 500.0 GiB) in 28s, read: 2.4 GiB/s, write: 0 B/s
INFO:  11% (55.2 GiB of 500.0 GiB) in 31s, read: 2.4 GiB/s, write: 101.3 KiB/s
INFO:  12% (62.4 GiB of 500.0 GiB) in 34s, read: 2.4 GiB/s, write: 0 B/s
INFO:  13% (69.5 GiB of 500.0 GiB) in 37s, read: 2.4 GiB/s, write: 10.7 KiB/s
INFO:  15% (76.6 GiB of 500.0 GiB) in 40s, read: 2.4 GiB/s, write: 1.3 KiB/s
INFO:  16% (83.7 GiB of 500.0 GiB) in 43s, read: 2.4 GiB/s, write: 21.3 KiB/s
INFO:  18% (90.8 GiB of 500.0 GiB) in 46s, read: 2.4 GiB/s, write: 0 B/s
INFO:  19% (97.9 GiB of 500.0 GiB) in 49s, read: 2.4 GiB/s, write: 0 B/s
INFO:  21% (105.0 GiB of 500.0 GiB) in 52s, read: 2.4 GiB/s, write: 21.3 KiB/s
INFO:  22% (111.3 GiB of 500.0 GiB) in 55s, read: 2.1 GiB/s, write: 9.9 MiB/s
INFO:  23% (116.8 GiB of 500.0 GiB) in 1m 3s, read: 712.6 MiB/s, write: 91.1 MiB/s
INFO:  24% (123.9 GiB of 500.0 GiB) in 1m 6s, read: 2.4 GiB/s, write: 0 B/s
INFO:  26% (130.9 GiB of 500.0 GiB) in 1m 9s, read: 2.3 GiB/s, write: 0 B/s
INFO:  27% (138.7 GiB of 500.0 GiB) in 1m 12s, read: 2.6 GiB/s, write: 0 B/s
INFO:  30% (150.1 GiB of 500.0 GiB) in 1m 15s, read: 3.8 GiB/s, write: 2.3 MiB/s
INFO:  31% (157.0 GiB of 500.0 GiB) in 1m 18s, read: 2.3 GiB/s, write: 0 B/s
INFO:  32% (164.0 GiB of 500.0 GiB) in 1m 21s, read: 2.3 GiB/s, write: 0 B/s
INFO:  34% (171.1 GiB of 500.0 GiB) in 1m 24s, read: 2.4 GiB/s, write: 42.7 KiB/s
INFO:  35% (178.1 GiB of 500.0 GiB) in 1m 27s, read: 2.3 GiB/s, write: 16.0 KiB/s
INFO:  37% (185.2 GiB of 500.0 GiB) in 1m 30s, read: 2.4 GiB/s, write: 0 B/s
INFO:  38% (192.2 GiB of 500.0 GiB) in 1m 33s, read: 2.4 GiB/s, write: 58.7 KiB/s
INFO:  39% (199.3 GiB of 500.0 GiB) in 1m 36s, read: 2.4 GiB/s, write: 21.3 KiB/s
INFO:  41% (206.4 GiB of 500.0 GiB) in 1m 39s, read: 2.4 GiB/s, write: 0 B/s
INFO:  42% (213.5 GiB of 500.0 GiB) in 1m 42s, read: 2.4 GiB/s, write: 0 B/s
INFO:  43% (217.6 GiB of 500.0 GiB) in 1m 45s, read: 1.4 GiB/s, write: 48.9 MiB/s
INFO:  44% (221.7 GiB of 500.0 GiB) in 1m 51s, read: 696.6 MiB/s, write: 94.1 MiB/s
INFO:  45% (228.8 GiB of 500.0 GiB) in 1m 54s, read: 2.3 GiB/s, write: 0 B/s
INFO:  47% (235.9 GiB of 500.0 GiB) in 1m 57s, read: 2.4 GiB/s, write: 0 B/s
INFO:  48% (242.4 GiB of 500.0 GiB) in 2m, read: 2.2 GiB/s, write: 0 B/s
INFO:  49% (249.4 GiB of 500.0 GiB) in 2m 3s, read: 2.3 GiB/s, write: 42.7 KiB/s
INFO:  51% (256.5 GiB of 500.0 GiB) in 2m 6s, read: 2.4 GiB/s, write: 621.3 KiB/s
INFO:  52% (263.5 GiB of 500.0 GiB) in 2m 9s, read: 2.4 GiB/s, write: 0 B/s
INFO:  53% (268.3 GiB of 500.0 GiB) in 2m 12s, read: 1.6 GiB/s, write: 0 B/s
INFO:  55% (275.3 GiB of 500.0 GiB) in 2m 15s, read: 2.4 GiB/s, write: 0 B/s
INFO:  56% (282.4 GiB of 500.0 GiB) in 2m 18s, read: 2.4 GiB/s, write: 34.7 KiB/s
INFO:  57% (289.4 GiB of 500.0 GiB) in 2m 21s, read: 2.3 GiB/s, write: 46.7 KiB/s
INFO:  59% (296.5 GiB of 500.0 GiB) in 2m 24s, read: 2.3 GiB/s, write: 13.3 KiB/s
INFO:  60% (303.5 GiB of 500.0 GiB) in 2m 27s, read: 2.4 GiB/s, write: 0 B/s
INFO:  62% (310.6 GiB of 500.0 GiB) in 2m 30s, read: 2.3 GiB/s, write: 0 B/s
INFO:  63% (317.6 GiB of 500.0 GiB) in 2m 33s, read: 2.3 GiB/s, write: 20.0 KiB/s
INFO:  64% (323.8 GiB of 500.0 GiB) in 2m 36s, read: 2.1 GiB/s, write: 10.6 MiB/s
INFO:  65% (325.9 GiB of 500.0 GiB) in 2m 43s, read: 311.9 MiB/s, write: 132.9 MiB/s
INFO:  66% (332.8 GiB of 500.0 GiB) in 2m 46s, read: 2.3 GiB/s, write: 21.3 KiB/s
INFO:  68% (340.0 GiB of 500.0 GiB) in 2m 49s, read: 2.4 GiB/s, write: 21.3 KiB/s
INFO:  69% (347.0 GiB of 500.0 GiB) in 2m 52s, read: 2.3 GiB/s, write: 118.7 KiB/s
INFO:  70% (354.0 GiB of 500.0 GiB) in 2m 55s, read: 2.3 GiB/s, write: 0 B/s
INFO:  72% (361.1 GiB of 500.0 GiB) in 2m 58s, read: 2.3 GiB/s, write: 665.3 KiB/s
INFO:  73% (368.1 GiB of 500.0 GiB) in 3m 1s, read: 2.3 GiB/s, write: 21.3 KiB/s
INFO:  75% (375.1 GiB of 500.0 GiB) in 3m 4s, read: 2.3 GiB/s, write: 988.0 KiB/s
INFO:  76% (382.1 GiB of 500.0 GiB) in 3m 7s, read: 2.3 GiB/s, write: 588.0 KiB/s
INFO:  77% (389.2 GiB of 500.0 GiB) in 3m 10s, read: 2.3 GiB/s, write: 22.7 KiB/s
INFO:  79% (396.2 GiB of 500.0 GiB) in 3m 13s, read: 2.4 GiB/s, write: 0 B/s
INFO:  80% (403.3 GiB of 500.0 GiB) in 3m 16s, read: 2.4 GiB/s, write: 0 B/s
INFO:  82% (410.4 GiB of 500.0 GiB) in 3m 19s, read: 2.4 GiB/s, write: 85.3 KiB/s
INFO:  83% (417.5 GiB of 500.0 GiB) in 3m 22s, read: 2.4 GiB/s, write: 601.3 KiB/s
INFO:  84% (424.5 GiB of 500.0 GiB) in 3m 25s, read: 2.3 GiB/s, write: 0 B/s
INFO:  86% (430.1 GiB of 500.0 GiB) in 3m 28s, read: 1.8 GiB/s, write: 16.4 MiB/s
INFO:  87% (435.3 GiB of 500.0 GiB) in 3m 47s, read: 284.1 MiB/s, write: 96.5 MiB/s
INFO:  88% (442.3 GiB of 500.0 GiB) in 3m 50s, read: 2.3 GiB/s, write: 0 B/s
INFO:  89% (447.6 GiB of 500.0 GiB) in 3m 53s, read: 1.7 GiB/s, write: 18.2 MiB/s
INFO:  90% (454.5 GiB of 500.0 GiB) in 4m 7s, read: 507.6 MiB/s, write: 83.1 MiB/s
INFO:  93% (465.1 GiB of 500.0 GiB) in 4m 10s, read: 3.5 GiB/s, write: 32.7 MiB/s
INFO:  94% (471.3 GiB of 500.0 GiB) in 4m 30s, read: 314.5 MiB/s, write: 105.4 MiB/s
INFO:  96% (482.6 GiB of 500.0 GiB) in 4m 33s, read: 3.8 GiB/s, write: 28.9 MiB/s
INFO:  97% (485.3 GiB of 500.0 GiB) in 4m 49s, read: 173.1 MiB/s, write: 105.4 MiB/s
INFO:  98% (492.0 GiB of 500.0 GiB) in 4m 52s, read: 2.2 GiB/s, write: 0 B/s
INFO:  99% (499.2 GiB of 500.0 GiB) in 4m 55s, read: 2.4 GiB/s, write: 0 B/s
INFO: 100% (500.0 GiB of 500.0 GiB) in 4m 56s, read: 847.5 MiB/s, write: 0 B/s
INFO: backup is sparse: 489.55 GiB (97%) total zero data
INFO: transferred 500.00 GiB in 296 seconds (1.7 GiB/s)
INFO: archive file size: 3.45GB
INFO: Finished Backup of VM 104 (00:04:56)
INFO: Backup finished at 2022-02-02 10:21:57
INFO: Backup job finished successfully
TASK OK

I really am Happy you have worked with me and Found a Better ( if you call it solution for now) at least you can know this was the actual issue
and maybe you guys can work on a fix for this setting

Kind Regards,
Spiro
 
  • Like
Reactions: oguz
Hi, every one! I have a similar situation. Every day after backup my VM not starting. QEMU Guest Agent installed. There are no critical issues in the logs. Tried backup mode Suspend/Stop. Guest system CentOS 7.
Code: 
backup task log
101: 2022-02-02 00:00:03 INFO: Starting Backup of VM 101 (qemu)
101: 2022-02-02 00:00:03 INFO: status = stopped
101: 2022-02-02 00:00:03 INFO: backup mode: stop
101: 2022-02-02 00:00:03 INFO: ionice priority: 7
101: 2022-02-02 00:00:03 INFO: VM Name: B24
101: 2022-02-02 00:00:03 INFO: include disk 'virtio0' 'local-zfs:vm-101-disk-1' 1592912M
101: 2022-02-02 00:00:03 INFO: snapshots found (not included into backup)
101: 2022-02-02 00:00:03 INFO: creating vzdump archive '/mnt/pve/synology/dump/vzdump-qemu-101-2022_02_02-00_00_02.vma.zst'
101: 2022-02-02 00:00:03 INFO: starting kvm to execute backup task
101: 2022-02-02 00:00:06 INFO: started backup task '6d2bb7b1-8135-4789-817a-7f20fcb9eab3'
101: 2022-02-02 01:10:01 INFO: 100% (1.5 TiB of 1.5 TiB) in 1h 9m 55s, read: 1.7 GiB/s, write: 4.0 KiB/s
101: 2022-02-02 01:10:01 INFO: backup is sparse: 1.10 TiB (72%) total zero data
101: 2022-02-02 01:10:01 INFO: transferred 1.52 TiB in 4195 seconds (379.7 MiB/s)
101: 2022-02-02 01:10:01 INFO: stopping kvm after backup task
101: 2022-02-02 01:10:02 INFO: archive file size: 372.27GB
101: 2022-02-02 01:10:02 INFO: Finished Backup of VM 101 (01:10:00)


Code: 
syslog
Feb 02 01:10:02 jupiter vzdump[2750540]: INFO: Finished Backup of VM 101 (01:10:00) Feb 02 01:10:02 jupiter vzdump[2750540]: INFO: Backup job finished successfully Feb 02 01:10:02 jupiter qmeventd[1324571]: Starting cleanup for 101 Feb 02 01:10:02 jupiter qmeventd[1324571]: Finished cleanup for 101 Feb 02 01:10:02 jupiter vzdump[2750474]: <root@pam> end task UPID:jupiter:0029F84C:0245453C:61F95902:vzdump:101:root@pam: OK

Any ideas about this? How to find out if the command is given to turn on the VM after backup?
 
Last edited:
yancherut said:
Hi, every one! I have a similar situation. Every day after backup my VM not starting. QEMU Guest Agent installed. There are no critical issues in the logs. Tried backup mode Suspend/Stop. Guest system CentOS 7.
Code: 
backup task log
101: 2022-02-02 00:00:03 INFO: Starting Backup of VM 101 (qemu)
101: 2022-02-02 00:00:03 INFO: status = stopped
101: 2022-02-02 00:00:03 INFO: backup mode: stop
101: 2022-02-02 00:00:03 INFO: ionice priority: 7
101: 2022-02-02 00:00:03 INFO: VM Name: B24
101: 2022-02-02 00:00:03 INFO: include disk 'virtio0' 'local-zfs:vm-101-disk-1' 1592912M
101: 2022-02-02 00:00:03 INFO: snapshots found (not included into backup)
101: 2022-02-02 00:00:03 INFO: creating vzdump archive '/mnt/pve/synology/dump/vzdump-qemu-101-2022_02_02-00_00_02.vma.zst'
101: 2022-02-02 00:00:03 INFO: starting kvm to execute backup task
101: 2022-02-02 00:00:06 INFO: started backup task '6d2bb7b1-8135-4789-817a-7f20fcb9eab3'
101: 2022-02-02 01:10:01 INFO: 100% (1.5 TiB of 1.5 TiB) in 1h 9m 55s, read: 1.7 GiB/s, write: 4.0 KiB/s
101: 2022-02-02 01:10:01 INFO: backup is sparse: 1.10 TiB (72%) total zero data
101: 2022-02-02 01:10:01 INFO: transferred 1.52 TiB in 4195 seconds (379.7 MiB/s)
101: 2022-02-02 01:10:01 INFO: stopping kvm after backup task
101: 2022-02-02 01:10:02 INFO: archive file size: 372.27GB
101: 2022-02-02 01:10:02 INFO: Finished Backup of VM 101 (01:10:00)


Code: 
syslog
Feb 02 01:10:02 jupiter vzdump[2750540]: INFO: Finished Backup of VM 101 (01:10:00) Feb 02 01:10:02 jupiter vzdump[2750540]: INFO: Backup job finished successfully Feb 02 01:10:02 jupiter qmeventd[1324571]: Starting cleanup for 101 Feb 02 01:10:02 jupiter qmeventd[1324571]: Finished cleanup for 101 Feb 02 01:10:02 jupiter vzdump[2750474]: <root@pam> end task UPID:jupiter:0029F84C:0245453C:61F95902:vzdump:101:root@pam: OK

Any ideas about this? How to find out if the command is given to turn on the VM after backup?
Click to expand...
What version of proxmox are you using. And is Centos7 installed with cPanel or just stand alone CentOS 7 ? Have you tried backup in snapshot mode ?
Thanks
 
Spirog said:
What version of proxmox are you using. And is Centos7 installed with cPanel or just stand alone CentOS 7 ? Have you tried backup in snapshot mode ?
Thanks
Click to expand...
Proxmox 7.0-11. Guest OS Centos7 without cPanel. Later i'm trying snapshot mode, but snapshot no warranty to be happy.
 
yancherut said:
Hi, every one! I have a similar situation. Every day after backup my VM not starting. QEMU Guest Agent installed. There are no critical issues in the logs. Tried backup mode Suspend/Stop. Guest system CentOS 7.
Code: 
...
101: 2022-02-02 00:00:03 INFO: status = stopped
101: 2022-02-02 00:00:03 INFO: backup mode: stop
...

Any ideas about this? How to find out if the command is given to turn on the VM after backup?
Click to expand...
your VM was off at the start of the backup already..
 
if you have an issue with a VM running, a backup starting, the VM being stopped by the backup and not resuming at the end - please post such a log. the log you posted is off a VM that was stopped before the backup, started (paused) for the backup, and returned to stop at the end. this is normal and expected behaviour and not a bug.
 
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