From: Alexander Burke via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Alexander Burke <alex@alexburke.ca>
Subject: Re: [PVE-User] Unresponsive VM(s) during VZdump
Date: Thu, 9 May 2024 11:24:06 +0000 (UTC) [thread overview]
Message-ID: <mailman.88.1715253871.319.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <2e504103-279a-4b24-a918-70d68e63220c@oeg.com.au>
[-- Attachment #1: Type: message/rfc822, Size: 5278 bytes --]
From: Alexander Burke <alex@alexburke.ca>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Unresponsive VM(s) during VZdump
Date: Thu, 9 May 2024 11:24:06 +0000 (UTC)
Message-ID: <11db3d6f-1879-44b3-9f99-01e6fde6ebc8@alexburke.ca>
Hello all,
My understanding is that if the backing store is ZFS, a snapshot of the zvol underlying the guest's disk(s) is instant and atomic, and the snapshot is what gets backed up so fleecing is moot. Am I wrong on this?
I know nothing about Ceph other than the fact that it supports snapshots; assuming the above understanding is correct, does snapshot-based backup not work much the same way on Ceph?
Cheers,
Alex
----------------------------------------
2024-05-09T10:11:20Z Mike O'Connor <mike@oeg.com.au>:
> 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
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
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 11:24 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
2024-05-09 11:24 ` Alexander Burke via pve-user [this message]
[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=mailman.88.1715253871.319.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alex@alexburke.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox