Am Fri, 17 Nov 2017 06:51:52 +0300
schrieb Andrei Borzenkov :
> 16.11.2017 19:13, Kai Krakow пишет:
> ...
> > > BTW: From user API perspective, btrfs snapshots do not guarantee
> > perfect granular consistent backups.
>
> Is it documented somewhere? I was relying on
16.11.2017 19:13, Kai Krakow пишет:
...
> > BTW: From user API perspective, btrfs snapshots do not guarantee
> perfect granular consistent backups.
Is it documented somewhere? I was relying on crash-consistent
write-order-preserving snapshots in NetApp for as long as I remember.
And I was sure
Link 2 slipped away, adding it below...
Am Tue, 14 Nov 2017 15:51:57 -0500
schrieb Dave :
> On Tue, Nov 14, 2017 at 3:50 AM, Roman Mamedov wrote:
> >
> > On Mon, 13 Nov 2017 22:39:44 -0500
> > Dave wrote:
> >
> > > I have my
Am Tue, 14 Nov 2017 15:51:57 -0500
schrieb Dave :
> On Tue, Nov 14, 2017 at 3:50 AM, Roman Mamedov wrote:
> >
> > On Mon, 13 Nov 2017 22:39:44 -0500
> > Dave wrote:
> >
> > > I have my live system on one block device and a
On Tue, Nov 14, 2017 at 3:50 AM, Roman Mamedov wrote:
>
> On Mon, 13 Nov 2017 22:39:44 -0500
> Dave wrote:
>
> > I have my live system on one block device and a backup snapshot of it
> > on another block device. I am keeping them in sync with hourly
On Mon, 13 Nov 2017 22:39:44 -0500
Dave wrote:
> I have my live system on one block device and a backup snapshot of it
> on another block device. I am keeping them in sync with hourly rsync
> transfers.
>
> Here's how this system works in a little more detail:
>
> 1. I
On Tue, 14 Nov 2017 10:14:55 +0300
Marat Khalili wrote:
> Don't keep snapshots under rsync target, place them under ../snapshots
> (if snapper supports this):
> Or, specify them in --exclude and avoid using --delete-excluded.
Both are good suggestions, in my case each system does
On 14/11/17 06:39, Dave wrote:
My rsync command currently looks like this:
rsync -axAHv --inplace --delete-delay --exclude-from="/some/file"
"$source_snapshop/" "$backup_location"
As I learned from Kai Krakow in this maillist, you should also add
--no-whole-file if both sides are local.
On Wed, Nov 1, 2017 at 1:15 AM, Roman Mamedov wrote:
> On Wed, 1 Nov 2017 01:00:08 -0400
> Dave wrote:
>
>> To reconcile those conflicting goals, the only idea I have come up
>> with so far is to use btrfs send-receive to perform incremental
>> backups
Am Thu, 2 Nov 2017 23:24:29 -0400
schrieb Dave :
> On Thu, Nov 2, 2017 at 4:46 PM, Kai Krakow
> wrote:
> > Am Wed, 1 Nov 2017 02:51:58 -0400
> > schrieb Dave :
> >
> [...]
> [...]
> [...]
> >>
> >> Thanks for
On Thu, Nov 2, 2017 at 4:46 PM, Kai Krakow wrote:
> Am Wed, 1 Nov 2017 02:51:58 -0400
> schrieb Dave :
>
>> >
>> >> To reconcile those conflicting goals, the only idea I have come up
>> >> with so far is to use btrfs send-receive to perform
Am Wed, 1 Nov 2017 02:51:58 -0400
schrieb Dave :
> >
> >> To reconcile those conflicting goals, the only idea I have come up
> >> with so far is to use btrfs send-receive to perform incremental
> >> backups
> >
> > As already said by Romain Mamedov, rsync is viable
[ ... ]
> The poor performance has existed from the beginning of using
> BTRFS + KDE + Firefox (almost 2 years ago), at a point when
> very few snapshots had yet been created. A comparison system
> running similar hardware as well as KDE + Firefox (and LVM +
> EXT4) did not have the performance
On Wed, Nov 1, 2017 at 4:34 AM, Marat Khalili wrote:
>> We do experience severe performance problems now, especially with
>> Firefox. Part of my experiment is to reduce the number of snapshots on
>> the live volumes, hence this question.
>
> Just for statistics, how many snapshots
On 01/11/17 09:51, Dave wrote:
As already said by Romain Mamedov, rsync is viable alternative to
send-receive with much less hassle. According to some reports it can even be
faster.
Thanks for confirming. I must have missed those reports. I had never
considered this idea until now -- but I like
On Wed, Nov 1, 2017 at 2:19 AM, Marat Khalili wrote:
> You seem to have two tasks: (1) same-volume snapshots (I would not call them
> backups) and (2) updating some backup volume (preferably on a different
> box). By solving them separately you can avoid some complexity...
Yes, it
On Wed, Nov 1, 2017 at 1:15 AM, Roman Mamedov wrote:
> On Wed, 1 Nov 2017 01:00:08 -0400
> Dave wrote:
>
>> To reconcile those conflicting goals, the only idea I have come up
>> with so far is to use btrfs send-receive to perform incremental
>> backups
I'm active user of backup using btrfs snapshots. Generally it works with
some caveats.
You seem to have two tasks: (1) same-volume snapshots (I would not call
them backups) and (2) updating some backup volume (preferably on a
different box). By solving them separately you can avoid some
On Wed, 1 Nov 2017 01:00:08 -0400
Dave wrote:
> To reconcile those conflicting goals, the only idea I have come up
> with so far is to use btrfs send-receive to perform incremental
> backups as described here:
> https://btrfs.wiki.kernel.org/index.php/Incremental_Backup
Our use case requires snapshots. btrfs snapshots are best solution we
have found for our requirements, and over the last year snapshots have
proven their value to us.
(For this discussion I am considering both the "root" volume and the
"home" volume on a typical desktop workstation. Also, all
20 matches
Mail list logo