From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using LVM snapshots for hourly backups
Date: Wed, 11 Oct 2006 08:25:49 -0500 [thread overview]
Message-ID: <bdb432dd699ec60a109bea3831d5d7d2@redhat.com> (raw)
In-Reply-To: <452BFBF9.3060301@overnetdata.com>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
I think everyone feels the same way about the current snapshot
implementation, and there is growing momentum for change. See
"[dm-devel] [RFC] DM Snapshot scalability - Common snap store approach"
(Oct 9th on dm-devel).
Certainly, any changes will take a while though.
brassow
On Oct 10, 2006, at 3:00 PM, Anthony Wright wrote:
> I'm trying to work out if there's a way to use LVM snapshots to create
> hourly backups of my data. I realise that this doesn't protect me
> against disk/machine failure, but it would really handy in cases where
> I want easy access to historical files, e.g where I accidentally
> change/delete a file or I want to compare historical files/directories
> to the current versions to see what's been changed.
>
> I thought a really simple and ingeneous approach would be to use LVM
> snapshots so that each hour I make a snapshot, and remove the snapshot
> from 24 hours ago, thus having a rolling hourly backup. However when I
> tried this I ended up with 24 snapshots of the original volume which
> means a single change to the original volume causes each snapshot to
> do a Copy on Write of the changed block, so if I change one block on
> the original volume the snapshots create 24 copies of the original
> volume which isn't very good for disk performance or disk usage!!
>
> What I'd really want is to daisy-chain the snapshots so that
> snapshot-3hours is a snapshot of snapshot-2hours, which is a snapshot
> of snapshot-1hour, which is a snapshot of the original volume, thus if
> a block in the original volume changes only snapshot-1hour is changed
> and once a snapshot is older than an hour it cannot change any more.
>
> I notice that you can't make snapshots of snapshots, so I suspect what
> I'm looking for isn't possible, but I thought I check and if it isn't
> possible suggest it as a really useful feature for the future. Your
> thoughts/comments would be welcome.
>
> Thanks,
>
> Tony Wright.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
[-- Attachment #2: Type: text/enriched, Size: 2140 bytes --]
I think everyone feels the same way about the current snapshot
implementation, and there is growing momentum for change. See
"<bold>[dm-devel] [RFC] DM Snapshot scalability - Common snap store
approach</bold>" (Oct 9th on dm-devel).
Certainly, any changes will take a while though.
brassow
On Oct 10, 2006, at 3:00 PM, Anthony Wright wrote:
<excerpt>I'm trying to work out if there's a way to use LVM snapshots
to create hourly backups of my data. I realise that this doesn't
protect me against disk/machine failure, but it would really handy in
cases where I want easy access to historical files, e.g where I
accidentally change/delete a file or I want to compare historical
files/directories to the current versions to see what's been changed.
I thought a really simple and ingeneous approach would be to use LVM
snapshots so that each hour I make a snapshot, and remove the snapshot
from 24 hours ago, thus having a rolling hourly backup. However when I
tried this I ended up with 24 snapshots of the original volume which
means a single change to the original volume causes each snapshot to
do a Copy on Write of the changed block, so if I change one block on
the original volume the snapshots create 24 copies of the original
volume which isn't very good for disk performance or disk usage!!
What I'd really want is to daisy-chain the snapshots so that
snapshot-3hours is a snapshot of snapshot-2hours, which is a snapshot
of snapshot-1hour, which is a snapshot of the original volume, thus if
a block in the original volume changes only snapshot-1hour is changed
and once a snapshot is older than an hour it cannot change any more.
I notice that you can't make snapshots of snapshots, so I suspect what
I'm looking for isn't possible, but I thought I check and if it isn't
possible suggest it as a really useful feature for the future. Your
thoughts/comments would be welcome.
Thanks,
Tony Wright.
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
</excerpt>
next prev parent reply other threads:[~2006-10-11 13:23 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 [this message]
2006-10-13 10:14 ` Nick
2006-10-13 10:22 ` Roger Lucas
2006-10-16 21:07 ` Greg Freemyer
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=bdb432dd699ec60a109bea3831d5d7d2@redhat.com \
--to=jbrassow@redhat.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).