How has it been for reliability?
I wrote a btrsync app a while back, and the app /itself/ worked fine,
but the btrfs send / btrfs receive itself proved problematic. Since
btrfs would keep a partial receive - with no easy way to tell whether a
receive WAS partial or full - I would inevitably end up with interrupted
sends causing a problem that couldn't be resolved without manually
deleting snapshots on the target end haphazardly until I nailed the
incomplete one.
On 08/11/2014 01:49 PM, Ames Cornish wrote:
I've written a utility to help me with using btrfs send and receive for
backups or other synchronization, and I'd love to get feedback on it.
As of this release, buttersink will synchronize a set of read-only snapshots
in a btrfs filesystem to an Amazon S3 bucket, and vice-versa. It
intelligently picks parent snapshots to "diff" from, so that a minimal amount
of data needs to be sent over the wire and stored in the backend.
The utility is on PyPi as "buttersink", and the GitHub page is here:
https://github.com/AmesCornish/buttersink.
Thanks in advance for any feedback!
- Ames
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
