From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using LVM snapshots for hourly backups
Date: Mon, 16 Oct 2006 17:07:44 -0400 [thread overview]
Message-ID: <87f94c370610161407j6b98d0aam3bb45969ed12962d@mail.gmail.com> (raw)
In-Reply-To: <20061013102208.0D52312EE1@bluewhale.planbit.co.uk>
On 10/13/06, Roger Lucas <roger@planbit.co.uk> wrote:
> Hi Nick,
>
> RSYNC is useful for this, but it works at the file level. If you had, for example, a 1GB e-mail file (e.g. Outlook PST) or a large
> database file, and it was getting small changes every day (e.g. receiving a dozen 10KB e-mails => 120KB of changes), then RSYNC
> would quickly eat up your disk space as each backup taken with RSYNC a complete new copy of the whole 1GB file.
>
> Cascaded LVM snapshots, on the other hand, would allow the just the changes within the files to be kept, dramatically reducing the
> disk usage.
>
> I'm sure that you know this already, but it was worth explicitly stating the difference between RSYCN and LVM snapshots in case
> someone reading the list wasn't as sure.
>
> BR,
>
> Roger
For now, you may want to checkout rdiff-backup. It uses rsync like
functionality to find deltas in your files and then it only backs up
the deltas.
IIRC, it actually keeps a current copy of your file, plus a series of
deltas that let you get to older versions.
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
prev parent reply other threads:[~2006-10-16 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 20:00 [linux-lvm] Using LVM snapshots for hourly backups Anthony Wright
2006-10-11 13:25 ` Jonathan E Brassow
2006-10-13 10:14 ` Nick
2006-10-13 10:22 ` Roger Lucas
2006-10-16 21:07 ` Greg Freemyer [this message]
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=87f94c370610161407j6b98d0aam3bb45969ed12962d@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=linux-lvm@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 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).