From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] backup hardware setup
Date: Tue, 24 Jun 2014 17:28:27 +0200 [thread overview]
Message-ID: <20140624152827.GB3908@solfire> (raw)
In-Reply-To: <53A99597.9060200@thegeezer.net>
thegeezer <thegeezer@thegeezer.net> [14-06-24 17:16]:
> On 06/24/2014 03:43 PM, meino.cramer@gmx.de wrote:
> > Hi,
> >
> > I bought two identical external harddrives, USB 3.0, with 1 TByte each
> > (no SSD - the good ole mechanical ones...;).
> >
> > The intended use is for backup of longer files. The drives will
> > contain the same contents.
> >
> > Currently there are still "clean metal" (no partitioning, no fs).
> >
> > Data integrity and recoverability (Uhhh...that words looks wrong...) in
> > case of an desaster is more important than speed.
> >
> > What is the recommended way of partitioning ?
> > What filesystem to choose?
> >
> >
> > Thank you very much in advance for any help!
> > Best regards,
> > mcc
> >
> >
> > PS: Running vanilla kernel 3.15.1....
> >
> >
> >
> >
>
> I do this using hard links and rsync to only copy changed data.
> this creates a dated folder structure that i can then rsync / cp using a
> livecd to baremetal and basically allows best recoverability, imho.
> so long as the filesystem supports hard links you are golden.
> you might want btrfs for this for long term storage to help in case of
> bitrot, but rsync should refresh the file if it is suddenly unreadable
> (meaning any other hard lnked versoins are also up the swanny)
> ymmv depending on what it is you are backing up
>
> #!/bin/bash
> echo 'preparing..'
> date=`date "+%Y-%m-%d_%H.%M.%S"`
> workingfolder="/mnt/usb/backupsyncs/myhost1"
> fromfolder="root@myhost1:/* --exclude=/var/tmp --exclude=/dev
> --exclude=/mnt --exclude=/opt --exclude=/proc --exclude=/sys
> --exclude=/usr/portage --exclude=/usr/src"
>
> echo "Date " $date
> echo "From " $fromfolder
> echo "To " $workingfolder
>
> echo "move current to be dated"
> mv $workingfolder/current $workingfolder/backup-$date
>
> echo "now syncing into dated folder"
> rsync -vz --partial --modify-window 5 -W --delete -a $fromfolder
> $workingfolder/backup-$date
>
> echo "cleaning up..linkcopying dated folder to <current>"
> cp -al $workingfolder/backup-$date $workingfolder/current
>
>
>
Hi,
thank you for your reply! :)
...I am sure, whether I want btrfs. On the net I found
for example this:
http://www.phoronix.com/scan.php?page=news_item&px=MTY1MDU
with sentences like:
"The Btrfs file-system changes for the Linux 3.15 kernel mostly deal
with bug fixes and performance fixes while some corruption fixes are
also expected to come."
...sounds a little different to "stable" I think...
What do you think?
next prev parent reply other threads:[~2014-06-24 15:29 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 [this message]
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
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=20140624152827.GB3908@solfire \
--to=meino.cramer@gmx.de \
--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