From: Nick <lists@mogmail.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using LVM snapshots for hourly backups
Date: Fri, 13 Oct 2006 11:14:07 +0100 [thread overview]
Message-ID: <452F66EF.5010005@mogmail.net> (raw)
In-Reply-To: <bdb432dd699ec60a109bea3831d5d7d2@redhat.com>
Sounds like it's not available in LVM but I achieve simmilar results
with rsync. Take a look at this for some pointers.
http://www.mikerubel.org/computers/rsync_snapshots/
Nick
Jonathan E Brassow wrote:
> 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
>
next prev parent reply other threads:[~2006-10-13 10:14 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 [this message]
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=452F66EF.5010005@mogmail.net \
--to=lists@mogmail.net \
--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.