From: Les Mikesell <lesmikesell@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Data deduplication in LVM?
Date: Thu, 11 Jun 2009 07:30:27 -0500 [thread overview]
Message-ID: <4A30F8E3.5090508@gmail.com> (raw)
In-Reply-To: <0CCC4321-943D-406A-A1BB-48E2BD6B0857@karlsbakk.net>
Roy Sigurd Karlsbakk wrote:
> On 11. juni. 2009, at 00.30, Stuart D. Gathman wrote:
>
>> One OSS backup product that does
>> deduplication is BackupPC (written in Perl). In the backup server,
>> every file
>> gets hard linked to a name in a special directory that is its md5
>> checksum
>> (plus some fiddly logic to handle metadata)
>
>
> This sounds like file-level deduplication. Most storage systems sing
> dedup, uses block-level dedup. NetApp is one example; they dedup
> everything with 4k blocks, doing the actual deduplication at night.
Yes, it is a different concept. However it does work very well when you
are storing your backups on a filesystem without block-level dedup. And
that is probably the place where you have the most redundancy - or if
you don't already, you'll be able to store a much longer history.
--
Les Mikesell
lesmikesell@gmail.com
next prev parent reply other threads:[~2009-06-11 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 18:41 [linux-lvm] Data deduplication in LVM? Roy Sigurd Karlsbakk
2009-06-10 18:48 ` Ray Van Dolson
2009-06-10 18:54 ` Les Mikesell
2009-06-10 18:59 ` Roy Sigurd Karlsbakk
2009-06-10 19:30 ` Les Mikesell
2009-06-10 19:33 ` Brian J. Murrell
2009-06-10 19:34 ` Ray Van Dolson
2009-06-10 19:04 ` Roy Sigurd Karlsbakk
2009-06-10 22:30 ` Stuart D. Gathman
2009-06-11 10:19 ` Roy Sigurd Karlsbakk
2009-06-11 12:30 ` Les Mikesell [this message]
2009-06-11 15:35 ` Les Mikesell
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=4A30F8E3.5090508@gmail.com \
--to=lesmikesell@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 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.