VM was silently skipped for backup with: config locked (backup)

S

SteveITS

Member
Feb 6, 2025
76
14
8
I've been working on a proof-of-concept for a cluster. Created a nightly backup job to experiment (not PBS). It only backed up one of two VMs last night. I see no attempt to back up VM 100 and no error? It is running, the status shows a floppy disk icon and the tooltip/hover shows "config locked (backup)." Log below.

Details​

VMID​
Name​
Status​
Time​
Size​
Filename​
101ns2-testok2m 24s1.658 GiB/mnt/pve/cephfs/dump/vzdump-qemu-101-2025_02_12-21_00_01.vma.zst

Total running time: 2m 24s
Total size: 1.658 GiB

Logs​

Code: 
vzdump --storage cephfs --quiet 1 --prune-backups 'keep-daily=3,keep-monthly=1,keep-weekly=2' --mode snapshot --notes-template '{{guestname}}' --fleecing 0 --compress zstd --all 1

101: 2025-02-12 21:00:01 INFO: Starting Backup of VM 101 (qemu)
101: 2025-02-12 21:00:01 INFO: status = running
...
101: 2025-02-12 21:02:25 INFO: prune older backups with retention: keep-daily=3, keep-monthly=1, keep-weekly=2
101: 2025-02-12 21:02:25 INFO: pruned 0 backup(s)
101: 2025-02-12 21:02:25 INFO: Finished Backup of VM 101 (00:02:24)

Any suggestions to diagnose/resolve?
 
When you backup a VM, it's config is locked so no change can be made until backup is done. When a backup task doesn't end properly (user stops it, destination full and the likes), PVE does not clean the status properly (yet) and the VM stays in "locked" state.

Use qm unlock <VMID> to remove the lock if you are 100% sure that there's no running backup on it.
 
Thanks.

Post-coffee, I see the cluster log actually does show it with a spinner for both end time and status, for: "VM/CT 100 - Backup".

VNC/console shows a connection timeout error after a while.

In the big picture I don't care about the VM as it's an empty/test server. But it would be better to have the backup log show some sort of failure.

Hmm, rereading the email...is the backup log email generated per node not per job? VM 100 is on node 2 and the log was from node 1.
 
Never mind, looks like node 2 was broken somehow...its PVE summary page updates fine but most other pages get a timeout and I can't log in to PVE directly, only SSH. :(

I ended up restarting it but this node also seems to take a half hour to boot for some reason. I'm remote so can't see it but am told it stops at a completely blank screen with a flashing cursor. It was a retired PC so something may be up with it but it's just for POC anyway.

Until this backup it had been running fine for a week.
 
You must log in or register to reply here.
Top Bottom