From: Gordon Henderson <gordon@drogon.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM & snapshots
Date: Tue, 20 Feb 2007 15:05:06 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0702201502430.27267@lion.drogon.net> (raw)
In-Reply-To: <20070220134026.GD7742@soda.linbit>
On Tue, 20 Feb 2007, Lars Ellenberg wrote:
> lvm works fine for me :-)
> but it won't work with 30 snapshots on one origin. not useful, anyways.
> it would work ok with two to three snapshots.
I wondered if that was the case - performance?
> but, just in case you want to stay with what you know,
> while optimizing it: to cut the time used for your cp -al:
> skip it. use the "--link-dest" option to rsync (I'm not sure which
> version of rsync you need, mine is 2.6.6).
My platforms are Debian sarge - rsync is 2.6.4, but they support the
--link-dest option (which would appear to be a new one for me!)
> so I would do a lvm snapshot on the source, then
> rsync $other_rsopts_like_include_exclude_whatever \
> -POazv '--log-format=%i %9l %n%L' \
> --link-dest /previous/backup /snapshot/mountpoint backupserver:/target
> (or, if you prefer to pull, pull...)
> and after that throw away the snapshot on the source machine again.
>
> so not "snapshots as backups" on the backup server,
> but as a means to get a consistent fs view on the source
> for the duration of the rsync.
Right. Thanks - I'll have a look into this. I actually have 2 of these
backup boxes, one on-site with the tape monster and one off-site, so this
may be just what's needed for the one with the tape unit.
Cheers,
Gordon
next prev parent reply other threads:[~2007-02-20 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 12:58 [linux-lvm] LVM & snapshots Gordon Henderson
2007-02-20 13:40 ` Lars Ellenberg
2007-02-20 15:05 ` Gordon Henderson [this message]
2007-02-20 13:47 ` Les Mikesell
2007-02-20 15:02 ` Gordon Henderson
2007-02-20 19:12 ` 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=Pine.LNX.4.64.0702201502430.27267@lion.drogon.net \
--to=gordon@drogon.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.