From: "J. Hart" <jfhart085@gmail.com>
To: Marat Khalili <mkh@rqc.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: backing up a file server with many subvolumes
Date: Mon, 27 Mar 2017 08:00:43 -0400 [thread overview]
Message-ID: <58D8FEEB.1080100@gmail.com> (raw)
In-Reply-To: <59dccd7e-6cb6-ea66-3150-0ce85472e73a@rqc.ru>
That is a very interesting idea. I'll try some experiments with this.
Many Thanks for the assistance....:-)
J. Hart
On 03/27/2017 01:57 AM, Marat Khalili wrote:
> Just some consideration, since I've faced similar but no exactly same
> problem: use rsync, but create snapshots on target machine. Blind
> rsync will destroy deduplication of your snapshots and take huge
> amount of storage, so it's not a solution. But you can rsync --inline
> your snapshots in chronological order to some folder and re-take
> snapshots of that folder, thus recreating your snapshots structure on
> target. Obviously, it can/should be automated.
>
>
next prev parent reply other threads:[~2017-03-27 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 3:00 backing up a file server with many subvolumes J. Hart
2017-03-26 9:14 ` Roman Mamedov
2017-03-26 19:51 ` Adam Borowski
2017-03-26 20:24 ` Peter Grandi
2017-03-27 5:57 ` Marat Khalili
2017-03-27 12:00 ` J. Hart [this message]
2017-03-27 13:05 ` Graham Cobb
2017-04-01 8:24 ` Kai Krakow
2017-03-27 11:53 ` Austin S. Hemmelgarn
2017-04-01 8:21 ` Kai Krakow
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=58D8FEEB.1080100@gmail.com \
--to=jfhart085@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mkh@rqc.ru \
/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