From: John Robinson <john.robinson@anonymous.org.uk>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: hansbkk@gmail.com, Jeff Klingner <klingner@stanford.edu>,
linux-raid@vger.kernel.org
Subject: Re: raid1 with rotating offsite disks for backup
Date: Thu, 10 Feb 2011 08:43:38 +0000 [thread overview]
Message-ID: <4D53A53A.2000409@anonymous.org.uk> (raw)
In-Reply-To: <AANLkTin6UFR6pR-E+z29kTd9VioRVxQqmOR-ABTnWymu@mail.gmail.com>
On 09/02/2011 19:53, Roberto Spadim wrote:
> i agree with rsync
> rsync is more filesystem related feature
> if you want copy files, you should use rsync
> if you want to copy the device, may be a dd with devices?
> dd if=/dev/md0 of=/dev/sda
>
> if you want a snapshot copy, you should first remount your filesystem
> to readonly (there´s no flock() for /dev/md0 since filesystem don´t
> use flock() on /dev/md0) or another way to block writes to filesystem
> while you is read from device, some filesystems have online backup
> features..
> i don´t know lvm very well, but maybe they implement online backup there...
> i don´t think it´s a problem to solve at md level (it could work, but
> the raid1 purpose is make a fail safe device (or partially safe), not
> a online backup device)
I do both with several of my customers: md array with LVM on top,
suspend system services (mailstore), take snapshot, start system
services, then rsync diff the snapshot to another drive with luks
crypto, which gets rotated off-site once a week. Generally the backup
drives are bigger than the system array, so I can keep at least a week's
worth of nightlies and several months' worth of weeklies on each one.
Yes, I have my own separate securely-stored copies of their crypto keys.
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-10 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 23:53 raid1 with rotating offsite disks for backup Jeff Klingner
2011-02-08 0:17 ` NeilBrown
2011-02-08 1:03 ` Jeff Klingner
2011-02-08 1:19 ` NeilBrown
2011-02-08 1:32 ` Jeff Klingner
2011-02-08 2:02 ` NeilBrown
2011-02-08 4:53 ` Leslie Rhorer
2011-02-08 5:37 ` Roberto Spadim
2011-02-08 6:07 ` NeilBrown
2011-02-08 6:12 ` Roberto Spadim
2011-02-08 3:04 ` Martin Cracauer
2011-02-08 3:40 ` Roberto Spadim
2011-02-09 19:37 ` hansbkk
2011-02-09 19:53 ` Roberto Spadim
2011-02-10 8:43 ` John Robinson [this message]
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=4D53A53A.2000409@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=hansbkk@gmail.com \
--cc=klingner@stanford.edu \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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.