public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] backup hardware setup
Date: Tue, 24 Jun 2014 22:08:54 +0100	[thread overview]
Message-ID: <53A9E8E6.10607@thegeezer.net> (raw)
In-Reply-To: <CAGfcS_k9-SvVetHUyhxXqhTvcX-vxcQASjO60QJghJXAoaEGsQ@mail.gmail.com>

On 06/24/2014 09:52 PM, Rich Freeman wrote:
> Don't ignore the potential for logical errors. If you have some script
> that magically rsyncs stuff then don't make the mistake of moving data
> over and rsyncing the old copy over the new, or mounting the devices
> in a manner that isn't robust when udev changes all your device
> labels, and so on. That seems like the most likely way your data is
> going to get scrambled, unless you have them both in your car and end
> up in a crash. That was one of the reasons I went with btrfs for my
> offline copy. 
cunning, i like it.
i like it so much i think i will do this myself
> If it unmounts, then I know I have two copies of everything. If it
> mounts, I know it found both mirrors. If I scrub and there are no
> errors, then I know both copies are good. You can do that in other
> ways, but make sure you actually catch the failure modes. Rich 



      reply	other threads:[~2014-06-24 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 14:43 [gentoo-user] backup hardware setup meino.cramer
2014-06-24 15:13 ` thegeezer
2014-06-24 15:28   ` meino.cramer
2014-06-24 15:47     ` thegeezer
2014-06-24 17:41     ` Rich Freeman
2014-06-24 17:06 ` Alan McKinnon
2014-06-24 17:32   ` meino.cramer
2014-06-24 17:56     ` Alan McKinnon
2014-06-24 18:34       ` meino.cramer
2014-06-24 20:02         ` Alan McKinnon
2014-06-24 20:52           ` Rich Freeman
2014-06-24 21:08             ` thegeezer [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=53A9E8E6.10607@thegeezer.net \
    --to=thegeezer@thegeezer.net \
    --cc=gentoo-user@lists.gentoo.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