[PVE-User] Unresponsive VM(s) during VZdump

Mike O'Connor mike at oeg.com.au
Thu May 9 12:11:04 CEST 2024


I played with all the drive interface settings, the end result was I 
lost customers because of backups causing windows drive failures.
Since fleecing was an option, I've not had a lockup.



On 9/5/2024 7:32 pm, Iztok Gregori wrote:
> Hi Mike!
>
> On 09/05/24 11:30, Mike O'Connor wrote:
>> You need to enable fleecing in the advanced backup settings. A slow 
>> backup storage system will cause this issue, configuring fleecing 
>> will fix this by storing changes in a local sparse image.
>
> I see that fleecing is available from PVE 8.2, I will enable it next 
> week once all the nodes will be upgraded to the latest version.
>
> Thanks for the suggestion.
>
> In the meantime I found this thread on the forum:
>
> https://forum.proxmox.com/threads/high-io-wait-during-backups-after-upgrading-to-proxmox-7.113790/ 
>
>
> which mention the max_workers parameter. I change it to 4 for the next 
> scheduled backup and see if there are some improvements (I migrated 
> the affected VMs to catch the new configuration).
>
> I will keep you posted!
>
> Iztok



More information about the pve-user mailing list