From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Block-Level Backup
Date: Thu Aug 7 11:33:01 2003 [thread overview]
Message-ID: <20030807163228.GC5036@ti19> (raw)
In-Reply-To: <20030807155421.GK381@fib011235813.fsnet.co.uk>
On Thu, Aug 07, 2003 at 04:54:21PM +0100, Joe Thornber wrote:
> This scheme only works if you don't use the device while you are
> taking an incremental backup. I think the real solution will be based
> around snapshots.
Right. But I think the point is this: one won't mind keeping multiple
(tower of hanoi) long-lived (week or more) block change indices, because
the performance impact should be very low.
When it it time to do an actual backup, we simultaneously create a
new block change index, take a regular snapshot, and freeze (or copy)
the block-change index of interest. Then we just back up the blocks
from the snapshot volume indicated in the frozen block-change index and
then delete the frozen block-change index and the snapshot volume.
For a typical filesystem, the snapshot volume persists for seconds to
minutes while the data is copied, not the tens of minutes to hours often
required to traverse the whole device with a tool like dump(8).
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2003-08-07 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 4:14 [linux-lvm] Block-Level Backup Rocky Lee
2003-08-07 4:28 ` Frank Van Damme
2003-08-07 4:34 ` Jose Luis Domingo Lopez
2003-08-07 4:37 ` Joe Thornber
2003-08-07 7:48 ` Christophe Saout
2003-08-07 8:45 ` Herbert Pötzl
2003-08-07 10:12 ` Bill Rugolsky Jr.
2003-08-07 10:55 ` Joe Thornber
2003-08-07 11:33 ` Bill Rugolsky Jr. [this message]
2003-08-07 12:39 ` Dieter Stueken
2003-08-08 8:46 ` Wolfgang Weisselberg
2003-08-07 8:28 ` Mark H. Wood
-- strict thread matches above, loose matches on Subject: below --
2003-08-07 3:02 Rocky Lee
2003-08-07 3:29 ` Markus Schiltknecht
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=20030807163228.GC5036@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=linux-lvm@sistina.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.