S subjectx Member Nov 4, 2020 36 3 8 113 Feb 3, 2021 #1 Greetings, One of the VMs should backup in the morning, but it didnt. In Logs, that wheel is spining in the line with Backup job description. Hard to restart VM, because it runs DB for alot of applications constantly in use. What to do?
Greetings, One of the VMs should backup in the morning, but it didnt. In Logs, that wheel is spining in the line with Backup job description. Hard to restart VM, because it runs DB for alot of applications constantly in use. What to do?
dylanw Proxmox Retired Staff Retired Staff Jul 6, 2020 373 87 28 Feb 3, 2021 #2 In case it's just a random, one off error, you can use qm unlock <vmid> to unlock the VM. If this throws any errors, please post the output. Otherwise, if the problem persists, please also post syslogs for around the time of the backup. Reactions: RubenCh00 and PhaseIV
In case it's just a random, one off error, you can use qm unlock <vmid> to unlock the VM. If this throws any errors, please post the output. Otherwise, if the problem persists, please also post syslogs for around the time of the backup.
S subjectx Member Nov 4, 2020 36 3 8 113 Feb 3, 2021 #3 Ahh, false alarm. One of the containers suddenly got big (intentionally) so first backup job took 12 hours. The problem with slow read/write on this server is still not solved, but will do this in separate thread.
Ahh, false alarm. One of the containers suddenly got big (intentionally) so first backup job took 12 hours. The problem with slow read/write on this server is still not solved, but will do this in separate thread.
J jamesz New Member Jul 16, 2023 5 0 1 Jul 27, 2023 #4 Thank-you dylanw, this work perfectly. qm unlock <vmid>