[Discuss] rsnapshot vs. rdiff-backup

[John Abreau]

It occurs to me that I'm thinking of LVM snapshots, and I'm assuming btrfs
is a filesystem that has LVM-like functionality baked in.


On Thu, Dec 5, 2013 at 11:00 AM, John Abreau <abreauj at gmail.com> wrote:

> A limitation of btrfs is that the snapshots are internal to the filesystem.
> Kind of makes it hard to put the snapshots on a separate machine.
>
>
> On Thu, Dec 5, 2013 at 9:47 AM, Edward Ned Harvey (blu)
> <blu at nedharvey.com>wrote:
>
> > > From: discuss-bounces+blu=nedharvey.com at blu.org [mailto:discuss-
> > > bounces+blu=nedharvey.com at blu.org] On Behalf Of Mike Small
> > >
> > > Does btrfs fit in here somewhere?
> >
> > Yes.  When you create a btrfs or zfs snapshot, and send incremental to
> the
> > destination system, that is perfectly analogous to rsnapshot sending the
> > incremental, except that btrfs and zfs will be much more efficient in
> terms
> > of time & space.
> >
> > Since rsnapshot is linux/unix only (requires hard links on destination)
> it
> > will eventually suffer a large percentage obsolescence by btrfs.  But for
> > now, btrfs isn't commonly enough deployed, commonly enough supported...
>  So
> > rsnapshot still has its place.
> >
> > rdiff-backup has a niche in cross-platform compatibility.  It makes an
> > effort to understand and intelligently translate the various
> implementation
> > details between different systems.  For example, different supported
> > character sets supported by EXT and NTFS, for example, a different
> concept
> > of permission bits and ACL's on different platforms.
> >
> > That being said, I'm officially the rdiff-backup maintainer, and I'm not
> > doing much maintenance.  With the introduction of so many new different
> > filesystems and different features and concepts on each one, it becomes
> > difficult to support interchangeability between all of them.  I'm not
> > saying it can't be done; I'm only saying it's work intensive.
> > _______________________________________________
> > Discuss mailing list
> > Discuss at blu.org
> > http://lists.blu.org/mailman/listinfo/discuss
> >
>
>
>
> --
> John Abreau / Executive Director, Boston Linux & Unix
> Email: abreauj at gmail.com / WWW http://www.abreau.net / PGP-Key-ID
> 0x920063C6
> PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23  C2D0 E885 E17C 9200 63C6
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
Email jabr at blu.org / WWW http://www.abreau.net / 2013 PGP-Key-ID 0x920063C6
2013 / ID 0x920063C6 / FP A5AD 6BE1 FEFE 8E4F 5C23  C2D0 E885 E17C 9200 63C6
2011 / ID 0x32A492D8 / FP 7834 AEC2 EFA3 565C A4B6  9BA4 0ACB AD85 32A4 92D8