From: "Jon Nelson" <jnelson-linux-raid@jamponi.net>
To: Drew <drew.kay@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Backups using RAID1
Date: Thu, 20 Nov 2008 09:33:15 -0600 [thread overview]
Message-ID: <cccedfc60811200733n4fee95degd3bb60ad9dbfe700@mail.gmail.com> (raw)
In-Reply-To: <c268e4660811200724x5a6a1fffueb2741ccc20006b1@mail.gmail.com>
Why not consider something like drbd or even something like this:
use AoE or iSCSI or NBD or *whatever* that exports a block device over
the network, and use *that* device in a bitmap-backed raid1.
(thus, your raid1 consists of /dev/sdX and /dev/etherd/e0.5 )
--
Jon
next prev parent reply other threads:[~2008-11-20 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 15:13 Backups using RAID1 Drew
[not found] ` <62c47030811191213n49a50624k4a0e167f20193a4@mail.gmail.com>
2008-11-20 2:11 ` Drew
2008-11-20 7:28 ` Max Waterman
2008-11-20 8:43 ` David Greaves
2008-11-20 15:24 ` Drew
2008-11-20 15:33 ` Jon Nelson [this message]
2008-11-20 16:12 ` Max Waterman
2008-11-20 22:20 ` Bill Davidsen
2008-11-20 9:08 ` Robin Hill
2008-11-20 11:48 ` David Greaves
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=cccedfc60811200733n4fee95degd3bb60ad9dbfe700@mail.gmail.com \
--to=jnelson-linux-raid@jamponi.net \
--cc=drew.kay@gmail.com \
--cc=linux-raid@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).