From: Bryan Whitehead <driver@megahappy.net>
To: Fred van Zwieten <fvzwieten@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: remote mirroring in the works?
Date: Mon, 30 Aug 2010 10:21:18 -0700 [thread overview]
Message-ID: <AANLkTi=ap5veJhyBsuWFJ3ppb2a_mSLiTu2YocAsQRBk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimBVG3eGHvNUHFGYri+JyOXrOW91GKWeM_GVOYM@mail.gmail.com>
LVM Snapshot.
lvm -s -n SnapShotName /dev/VolumeGroup/SourceLogicalVolumeName
you may need to pass -l or -L to give an initial size for the COW.
(as for rebuilding on another machine, that would require shared
storage or additional LVM tricks to export/import - or good old
fashioned dd)
that said, a more appropriate list to question is linux-lvm@redhat.com
On Mon, Aug 30, 2010 at 10:07 AM, Fred van Zwieten <fvzwieten@gmail.com=
> wrote:
> Hi there,
>
> I would like to know if there is something functionally equivalent to
> NetApp's SnapMirror in the works or planning? It would require block
> level access to a snap and the ability to rebuild (subvolumes
> including it's) snap's on another machine.
>
> If not, what would be the best way to build something more or less
> equivalent using existing tools? rsync-ing a snap seems the same, but
> it isn't. First of all it 's file based, not very nice for DB's, and
> you don't get the snap's on "the other side" the same.
>
> Fred
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-30 17:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinmSdHwXXq3s64sM39GjacafgwgTjPadZGHuway@mail.gmail.com>
2010-08-30 17:07 ` remote mirroring in the works? Fred van Zwieten
2010-08-30 17:21 ` Bryan Whitehead [this message]
2010-08-30 17:33 ` Roy Sigurd Karlsbakk
2010-08-30 17:55 ` K. Richard Pixley
2010-08-30 17:59 ` Roy Sigurd Karlsbakk
2010-08-30 18:14 ` K. Richard Pixley
2010-08-31 6:30 ` Simon Kirby
2010-08-31 18:44 ` Fred van Zwieten
2010-09-06 21:50 ` David Nicol
2010-09-07 0:04 ` K. Richard Pixley
2010-08-30 21:15 ` Fred van Zwieten
2010-08-30 21:23 ` Freddie Cash
2010-08-30 22:56 ` K. Richard Pixley
2010-08-31 5:07 ` Fred van Zwieten
2010-08-31 6:38 ` Simon Kirby
2010-08-31 18:29 ` Goffredo Baroncelli
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='AANLkTi=ap5veJhyBsuWFJ3ppb2a_mSLiTu2YocAsQRBk@mail.gmail.com' \
--to=driver@megahappy.net \
--cc=fvzwieten@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).