Difficulties with vzdump

[clgies]

Hi Folks,

We currently have the problem that backup operations are not running correctly (pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-27-pve))

Although a 100% backup was performed according to the Proxmox backend user interface, the vzdump logs indicate a backup failure.

In addition, the canceled backup processes persist and cannot be deleted (even though vzdump.lock and vzdump.pid were executed before the kill -9 $ pid).

What has to be done now?

A restart of the Proxmox host? Can restarting the Proxmox host cause inconsistencies if the backup is not completed?

We are grateful for every tip.

Many Thanks,
Claus

root      4893  0.0  0.1 527924 85812 ?        Ds   Apr20   0:00 task UPID:d10239:0000131D:0363F19E:5E9D0222:vzdump::root@pam:
root      8330  0.0  0.0 578456 44920 ?        Ds   Oct14   0:05 task UPID:d10239:0000208A:5E763C50:5F8626B8:vzdump:103:root@pam:
root     29193  0.0  0.0 578004 42776 ?        Ds   Oct13   0:05 task UPID:d10239:00007209:5E6B5C06:5F860AE1:vzdump:103:root@pam:

 

[Dominic]

Hi Folks,

We currently have the problem that backup operations are not running correctly (pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-27-pve))

Proxmox VE 5 is at end of life. I strongly suggest upgrading to version 6.

Although a 100% backup was performed according to the Proxmox backend user interface, the vzdump logs indicate a backup failure.

I don't see any error message in your screenshots?

In addition, the canceled backup processes persist and cannot be deleted (even though vzdump.lock and vzdump.pid were executed before the kill -9 $ pid).

What has to be done now?

The 100% are for the actual copying process. There is still some configuration stuff going on after that, that might take some time (shouldn't be long). The whole thing is finished when the task log/viewer says "TASK OK".

 

[clgies]

Proxmox VE 5 is at end of life. I strongly suggest upgrading to version 6.


I don't see any error message in your screenshots?

Plz. have a look at Picture 2) The Backup Process breaks without any errors, but breaks and remains zombie Tasks.

The 100% are for the actual copying process. There is still some configuration stuff going on after that, that might take some time (shouldn't be long). The whole thing is finished when the task log/viewer says "TASK OK".

In addition, the canceled backup processes persist and cannot be deleted (even though vzdump.lock and vzdump.pid were executed before the kill -9 $ pid).

What has to be done now?

 

[clgies]

Please take a look at picture 2. The backup process is interrupted 72% without errors, but it aborts and remains zombie tasks.

I ask again what to do. Restart the Proxmox host to get rid of the zombie tasks? Can that damage the virtual machines?

@Dominic Unfortunately, your last answers were far from helpful.