From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Which better: rsync or snapshot + rsync --delete
Date: Sat, 03 Aug 2013 18:54:18 +0200 [thread overview]
Message-ID: <s6pvca-4tt.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: kthh5l$7ti$1@ger.gmane.org
Martin <m_btrfs@ml1.co.uk> schrieb:
> Which is 'best' or 'faster'?
>
> Take a snapshot of an existing backup and then "rsync --delete" into
> that to make a backup of some other filesystem?
>
> Or use "rsync --link" to link a new backup tree against a previous
> backup tree for the some other filesystem?
I'm doing it vice-versa... I rsync --inplace --delete to a scratch area and
only then after that finished without errors, I'm taking a snapshot of that.
That way I always know the snapshots are in good and consistent state while
the scratch area is just playground for in-progress backups.
Just in case you are curious, here's the gist:
https://gist.github.com/kakra/5520370
Using inplace and no-whole-file options ensures space-efficient snapshots. I
don't worry about fragmentation, it's only the backup drive. It doesn't
matter if it's fragmented and thus a little bit slower, it only matters
restore works fine.
It is using systemd for automation but feel free to call it from cron...
HTH
Kai
prev parent reply other threads:[~2013-08-03 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 23:59 Which better: rsync or snapshot + rsync --delete Martin
2013-08-03 7:57 ` Bart Noordervliet
2013-08-03 16:54 ` Kai Krakow [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=s6pvca-4tt.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@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 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.