From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds?
Date: Mon, 29 Nov 2010 17:27:56 +0100 [thread overview]
Message-ID: <20101129162756.GN16420@barkeeper1-xen.linbit> (raw)
In-Reply-To: <AANLkTimGkMJGiJC+7L+Pu3+yf-J_s0Ex3hM2-g-0+UqQ@mail.gmail.com>
On Sun, Nov 28, 2010 at 10:31:51PM +0700, hansbkk@gmail.com wrote:
> �- - - - - - My abject apologies to all for improper addressing in my
> previous messages (thanks to all those who set me straight :)
>
> Hope you're all still willing to consider my request for feedback.
> Start with a bit of context:
>
> - SAN/NAS (call it FILER-A) hosting say a dozen TB and servicing a few
> dozen client machines and servers, mostly virtual hosts. Another,
> larger (FILER-B - still just tens of TB) host's drives are used for
> storing backup sets, via not only Amanda, but also filesystems
> comprising gazillions of hard-linked archive sets created by (eg)
> rdiff-backup, rsnapshot and BackupPC. We're on a very limited budget,
> therefore no tape storage for backups.
>
> - I plan to run LVM over RAID (likely RAID1 or RAID10) for IMO an
> ideal combination of fault tolerance, performance and flexibility.
>
> - I am not at this point overly concerned about performance issues -
> reliability/redundancy and ease of recovery are my main priorities.
>
>
> Problem:
>
> For off-site data rotation, the hard-linked filesystems on FILER-B
> require full filesystem cloning with block-level tools rather than
> file-level copying or sync'ing. My current plan is to swap out disks
> mirrored via RAID, marking them as "failed" and then rebuilding using
> the (re-initialized) incoming rotation set.
Did you consider DRBD?
Use DRBD, protocol A, potentially with drbd-proxy in between to mitigate
impact on primary site performance due to high latency connection to the
desaster recovery site.
At your option have it replicate continuously, or cron-job triggered
sync it up every "rotation interval", then disconnect again.
Depending on what you want, you can have one DRBD on top of
each LV, or have one DRBD by the PV of a VG.
Depending on what you do to the devices on the DR site,
you will likely be able to always do an incremental resync only
(ship only blocks that changed).
If you want to discuss that further, feel free to followup here,
on drbd-user, on freenode #drbd, or contact LINBIT directly.
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD� and LINBIT� are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2010-11-29 16:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimTYse7vnqZydc1Z5z60vNuQw3juj7J_W7+bQEm@mail.gmail.com>
2010-11-28 15:31 ` [linux-lvm] Q: LVM over RAID, or plain disks? A:"Yes" = best of both worlds? hansbkk
2010-11-29 16:27 ` Lars Ellenberg [this message]
2010-11-29 17:00 ` hansbkk
2010-11-29 18:57 ` Nataraj
2010-11-30 5:20 ` hansbkk
2010-11-30 7:14 ` Nataraj
2010-11-30 7:34 ` hansbkk
2010-11-30 13:13 ` Phil Turmel
2010-11-30 15:39 ` hansbkk
2010-11-30 16:56 ` Phil Turmel
2010-12-01 4:45 ` hansbkk
2010-12-01 12:50 ` Phil Turmel
2010-12-01 19:47 ` hansbkk
2010-11-30 15:41 ` Andrew Gideon
2010-11-30 15:53 ` hansbkk
2010-11-30 15:54 ` hansbkk
[not found] ` <2D.98.07087.690A2FC4@cdptpa-omtalb.mail.rr.com>
2010-11-29 11:01 ` [linux-lvm] " hansbkk
2010-11-29 15:29 ` Keld Jørn Simonsen
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=20101129162756.GN16420@barkeeper1-xen.linbit \
--to=lars.ellenberg@linbit.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).