P
penrose
Guest
Hello,
I have two servers with Proxmox 1.8.
They are configured the same way, and I ran on both the reduction of the LVM volume to create a second volume to back up using snapshots with vzdump instead of suspend.
On a server it all works regularly, while the other stops.
Vzdump without problems copy the configuration files; create snapshots (snapshot perfectly usable, I tried to copy the raw file from that and it worked without problems); then the vmtar to pick up the raw file and copy to file with suffix ".dat" in the backup directory. This dat file is always aa zero size, while vmtar at 100% cpu usage, and remain indefinitely in this state.
I tried several VM, I tried with snapshot and suspend, I tried with and without compression.
The result is the same.
The same VM (copied on the HD of the server) is bcked without problems from the other server.
Can anyone help me?
I have two servers with Proxmox 1.8.
They are configured the same way, and I ran on both the reduction of the LVM volume to create a second volume to back up using snapshots with vzdump instead of suspend.
On a server it all works regularly, while the other stops.
Vzdump without problems copy the configuration files; create snapshots (snapshot perfectly usable, I tried to copy the raw file from that and it worked without problems); then the vmtar to pick up the raw file and copy to file with suffix ".dat" in the backup directory. This dat file is always aa zero size, while vmtar at 100% cpu usage, and remain indefinitely in this state.
I tried several VM, I tried with snapshot and suspend, I tried with and without compression.
The result is the same.
The same VM (copied on the HD of the server) is bcked without problems from the other server.
Can anyone help me?
Last edited by a moderator:
