From: "Karl O. Pinc" <kop@meme.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: mauelshagen@redhat.com
Subject: Re: [linux-lvm] Difference in LVM and LVM2 and their strength/weakness
Date: Mon, 23 Jan 2006 13:56:13 +0000 [thread overview]
Message-ID: <1138024573l.3950l.2l@mofo> (raw)
In-Reply-To: <E8AFFEFDBE97C94E9297963F0527A07B07AC77@pmi00exf00.us.packetmotion.com> (from achen@packetmotion.com on Sun Jan 22 20:16:33 2006)
On 01/22/2006 08:16:33 PM, Alex Chen wrote:
> Heinz, thanks for the information/
>
> The main intention of our interest of LIME to use it for snapshots.
> I am told that it is a very quick way to make backups. Is that true?
(LIME?)
To be pedantic, LVM is absolutely not a backup. You can use it to make
backups from a known state of the system while the system continues to
be updated. Note that unless you've a way to force your appilcations,
databases, etc. into a known/internally consistent state at the moment
the sanapshot is created this quality is of questionable merit. YMMV.
If you trash the filesystem by crashing the disk, etc., your lvm
snapshot will be trashed too. Hence, not a backup.
See, for example, rsync with --link-dest for a way to make
backups from your snapshot that retain snapshot-like
disk utilization properties.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2006-01-23 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 2:16 [linux-lvm] Difference in LVM and LVM2 and their strength/weakness Alex Chen
2006-01-23 9:40 ` Heinz Mauelshagen
2006-01-23 13:56 ` Karl O. Pinc [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 19:23 Alex Chen
2006-01-23 21:23 ` Heinz Mauelshagen
2006-01-21 1:54 Alex Chen
2006-01-21 17:08 ` Heinz Mauelshagen
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=1138024573l.3950l.2l@mofo \
--to=kop@meme.com \
--cc=linux-lvm@redhat.com \
--cc=mauelshagen@redhat.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.