From: james northrup <northrup.james@gmail.com>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Possible to dedpulicate read-only snapshots for space-efficient backups
Date: Mon, 6 May 2013 07:35:41 -0700 [thread overview]
Message-ID: <CAPkEcwgAH=w7q5JdsJB+YLxDgysOwTUg7boyZFMmfB1v3fmwCw@mail.gmail.com> (raw)
In-Reply-To: <lj3k5a-6dh.ln1@hurikhan.ath.cx>
tried a git based backup? sounds spot-on as a compromise prior to
applying btrfs tweaks. snapshotting the git binaries would have the
dedupe characteristics.
On Mon, May 6, 2013 at 12:44 AM, Kai Krakow <hurikhan77+btrfs@gmail.com> wrote:
> Jan Schmidt <list.btrfs@jan-o-sch.net> schrieb:
>
>>> I'm using an bash/rsync script[1] to backup my whole system on a nightly
>>> basis to an attached USB3 drive into a scratch area, then take a snapshot
>>> of this area. I'd like to have these snapshots immutable, so they should
>>> be read-only.
>>
>> Have you considered using btrfs send / receive for that purpose? You would
>> just save the dedup step.
>
> This is planned for later. In the first step I want to stay as file system
> agnostic for the source as possible. But I've put it on my todo list in the
> gist.
>
> Regards,
> Kai
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-06 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-05 10:07 Possible to dedpulicate read-only snapshots for space-efficient backups Kai Krakow
2013-05-05 12:55 ` Gabriel de Perthuis
2013-05-05 17:22 ` Kai Krakow
2013-05-07 22:07 ` Gabriel de Perthuis
2013-05-07 23:04 ` Kai Krakow
2013-05-07 23:22 ` Kai Krakow
2013-05-07 23:35 ` Possible to deduplicate " Gabriel de Perthuis
2013-05-06 6:15 ` Possible to dedpulicate " Jan Schmidt
2013-05-06 7:44 ` Kai Krakow
2013-05-06 14:35 ` james northrup [this message]
2013-05-06 20:48 ` 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='CAPkEcwgAH=w7q5JdsJB+YLxDgysOwTUg7boyZFMmfB1v3fmwCw@mail.gmail.com' \
--to=northrup.james@gmail.com \
--cc=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.