[rear-users] Btrfs subvolume snapshots backup and restore
schlomo at schapiro.org
Sat Sep 28 22:48:21 CEST 2013
OK, so do we all agree that ReaR can use only the tools that already exist?
As long as there is no "smart" btrfs backup tool there is not much we can
BTW, should we automatically exclude the snapshot subvolumes? Or offer an
option for that? Otherwise people might not be able to use ReaR with NETFS
or RSYNC backup on btrfs systems any more.
If you think so then please kindly open a GitHub issue for that.
I also think that the loss of snapshots could be forgiven in the case of a
real disaster that made you recover the server on fresh hardware :-) After
all all snapshot systems utilize the same disks for the snapshots and don't
offload the snapshots to secure storage.
On 25 September 2013 20:52, Les Mikesell <lesmikesell at gmail.com> wrote:
> On Wed, Sep 25, 2013 at 10:49 AM, Johannes Meixner <jsmeix at suse.de> wrote:
> > Wow!
> > I have 70G of accessible files stored on my 7.1G disk
> > and still have 59% free space there ;-)
> > If I made an usual file-based backup of '/' (e.g. via 'tar')
> > I got a tarball with 70G that I cannot restore on my 7.1G disk.
> Wouldn't an appropriate solution be to back it up to a system that
> offers its own de-dup mechanism like btrfs/zfs with the option
> enabled, backuppc, rdiff-backup, etc.? That wouldn't really give
> you the snapshots back, but you would have the ability to restore
> files back from the time any backup was taken (just like you can with
> any other filesystem type) without needing extra storage for the
> versions that don't change.
> Les Mikesell
> lesmikesell at gmail.com
> rear-users mailing list
> rear-users at lists.relax-and-recover.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rear-users