archive mirror
 help / color / mirror / Atom feed
From: Gionatan Danti <>
To: LVM general discussion and development <>
Cc: "Gaikwad, Hemant" <>
Subject: Re: [linux-lvm] Need inputs: Performance issues with LVM snapshots
Date: Mon, 07 Mar 2022 15:44:27 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Il 2022-03-07 12:09 Gaikwad, Hemant ha scritto:
> Hi,
> We have been looking at LVM as an option for long term backup using
> the LVM snapshots. After looking at the various forums and also
> looking at a few LVM defects, realized that LVM could be a very good
> option for short term backup, but might result in performance issues
> if the snapshots are retained for a long time. Also read we should
> restrict the number of snapshots. We are thinking of keeping it to 3,
> but do you think that could also be a performance bottleneck. A few
> forum posts also suggest memory issues with using LVM snapshots. Can
> you please help with some data on that too. Thanks in advance for
> making our decision easier. Thanks
> Regards,

Classical, non-thin LVM snapshots are only meant to be short-lived (just 
enough to take a backup), and the performance penalty you talk about 
does apply.
Thin LVM snapshots, on the other side, command a much lower performance 
penalty and can be long-lived (ie: think about a rolling snapshot 
So if you need multiple, long-lived snapshots, I strongly suggest you to 
check lvmthin.

Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. -
email: -
GPG public key ID: FF5F32A8

linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2022-03-07 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 11:09 [linux-lvm] Need inputs: Performance issues with LVM snapshots Gaikwad, Hemant
2022-03-07 14:44 ` Gionatan Danti [this message]
2022-03-07 14:49   ` Demi Marie Obenour

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).