From: Mike O'Connor <mike@oeg.com.au>
To: Iztok Gregori <iztok.gregori@elettra.eu>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Unresponsive VM(s) during VZdump
Date: Thu, 9 May 2024 19:41:04 +0930 [thread overview]
Message-ID: <2e504103-279a-4b24-a918-70d68e63220c@oeg.com.au> (raw)
In-Reply-To: <2b94dfec-54d4-4a48-a379-01ef15713da5@elettra.eu>
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
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-05-09 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 8:35 Iztok Gregori
2024-05-09 9:30 ` Mike O'Connor
2024-05-09 10:02 ` Iztok Gregori
2024-05-09 10:11 ` Mike O'Connor [this message]
2024-05-09 11:24 ` Alexander Burke via pve-user
[not found] ` <11db3d6f-1879-44b3-9f99-01e6fde6ebc8@alexburke.ca>
2024-05-10 5:21 ` Mike O'Connor
2024-05-10 9:07 ` Fiona Ebner
2024-05-10 7:36 ` Iztok Gregori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e504103-279a-4b24-a918-70d68e63220c@oeg.com.au \
--to=mike@oeg.com.au \
--cc=iztok.gregori@elettra.eu \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.