* btrfs send and an existing backup
@ 2014-11-19 15:58 Jakob Schürz
2014-11-20 12:05 ` Marc Joliet
2014-11-20 13:17 ` Bardur Arantsson
0 siblings, 2 replies; 5+ messages in thread
From: Jakob Schürz @ 2014-11-19 15:58 UTC (permalink / raw)
To: linux-btrfs
Hi there!
I'm new on btrfs, and I like it :)
But i have a question. I have a existing backup on an external HDD. This
was ext4 before i converted it to btrfs.
And i installed my debian new on btrfs with some subvolumes. (f.e. home,
var, multimedia/Video multimedia/Audio...)
On my backup there are no subvolumes.
Now i wrote a script to take local snapshots on my laptops HDD an mirror
this snapshots with btrfs send/receive to the external HDD.
An i don't know, how to do, to make the inital snapshot on the external
HDD. I want to use the existing data there, so I don't have to transmit
the whole bunch of data to the external drive, which exists there
already...
What happens, if i make the same structure on the external drive with
creating subvolumes and »cp --reflink«, give this subvolumes the correct
names, and fire a »btrfs send«?
Or is the best (ONLY???) way, to make an initial snapshot on the
external drive and delete the old backup there?
greetings
jakob
--
http://xundeenergie.at
http://verkehrsloesungen.wordpress.com/
http://cogitationum.wordpress.com/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs send and an existing backup
2014-11-19 15:58 btrfs send and an existing backup Jakob Schürz
@ 2014-11-20 12:05 ` Marc Joliet
2014-11-20 13:17 ` Bardur Arantsson
1 sibling, 0 replies; 5+ messages in thread
From: Marc Joliet @ 2014-11-20 12:05 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 2870 bytes --]
Am Wed, 19 Nov 2014 16:58:16 +0100
schrieb Jakob Schürz <wertstoffe@nurfuerspam.de>:
> Hi there!
>
> I'm new on btrfs, and I like it :)
Me too :) . (I've been using it since May.)
> But i have a question. I have a existing backup on an external HDD. This
> was ext4 before i converted it to btrfs.
> And i installed my debian new on btrfs with some subvolumes. (f.e. home,
> var, multimedia/Video multimedia/Audio...)
>
> On my backup there are no subvolumes.
>
> Now i wrote a script to take local snapshots on my laptops HDD an mirror
> this snapshots with btrfs send/receive to the external HDD.
Yeah, I also recently made the switch to btrfs send/receive, and I just love
being able to do incremental full system backups in less than two minutes (it's
also efficient enough that I backup my (borrowed) laptop over WLAN).
So from me a big thanks to the btrfs devs :) !
But to get to the questions:
> An i don't know, how to do, to make the inital snapshot on the external
> HDD. I want to use the existing data there, so I don't have to transmit
> the whole bunch of data to the external drive, which exists there
> already...
Yeah, I had that problem, too, with my old rsync based backups; see below.
> What happens, if i make the same structure on the external drive with
> creating subvolumes and »cp --reflink«, give this subvolumes the correct
> names, and fire a »btrfs send«?
Do you mean cp --reflink from the original backup to the new structure? That
won't help. Again, see below.
> Or is the best (ONLY???) way, to make an initial snapshot on the
> external drive and delete the old backup there?
I couldn't think of any other way than doing an initial snapshot + send that
transferred the entire subvolumes, then doing incremental sends from there.
Here's my understanding as a complete non-expert:
The problem is that you need a parent snapshot, which needs to be on *both* the
source *and* target volumes, with which to be able to generate and then receive
the incremental send. Currently, your source and target volumes are
independent, so btrfs can't infer anything about any differences between them;
that is, while the data may be related, the file systems themselves have
independent "histories", making it impossible to compare them via their data
structures.
This is why you need to make an initial send: to give both volumes a common
frame of reference, so to speak.
So I bit the bullet and went through with it, and am keeping the original
backups until enough snapshots have accumulated in the new backup location
(both of my backups are on the same file system in different subvolumes).
> greetings
> jakob
HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs send and an existing backup
2014-11-19 15:58 btrfs send and an existing backup Jakob Schürz
2014-11-20 12:05 ` Marc Joliet
@ 2014-11-20 13:17 ` Bardur Arantsson
2014-11-20 14:10 ` Duncan
1 sibling, 1 reply; 5+ messages in thread
From: Bardur Arantsson @ 2014-11-20 13:17 UTC (permalink / raw)
To: linux-btrfs
On 2014-11-19 16:58, Jakob Schürz wrote:
> Hi there!
>
> I'm new on btrfs, and I like it :)
>
> But i have a question. I have a existing backup on an external HDD. This
> was ext4 before i converted it to btrfs.
> And i installed my debian new on btrfs with some subvolumes. (f.e. home,
> var, multimedia/Video multimedia/Audio...)
>
If you have no other backups, I would really recommend that you *don't*
use btrfs for your backup, or at least have a *third* backup which isn't
on btrfs -- there are *still* problems with btrfs that can potentially
wreck your backup filesystem. (Although it's obviously less likely if
the external HDD will only be connected occasionally.)
Don't get me wrong, btrfs is becoming more and more stable, but I
wouldn't trust it with my *only* backup, especially if also running
btrfs on the backed-up filesystem.
Regards,
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs send and an existing backup
2014-11-20 13:17 ` Bardur Arantsson
@ 2014-11-20 14:10 ` Duncan
2014-11-21 12:51 ` Austin S Hemmelgarn
0 siblings, 1 reply; 5+ messages in thread
From: Duncan @ 2014-11-20 14:10 UTC (permalink / raw)
To: linux-btrfs
Bardur Arantsson posted on Thu, 20 Nov 2014 14:17:52 +0100 as excerpted:
> If you have no other backups, I would really recommend that you *don't*
> use btrfs for your backup, or at least have a *third* backup which isn't
> on btrfs -- there are *still* problems with btrfs that can potentially
> wreck your backup filesystem. (Although it's obviously less likely if
> the external HDD will only be connected occasionally.)
>
> Don't get me wrong, btrfs is becoming more and more stable, but I
> wouldn't trust it with my *only* backup, especially if also running
> btrfs on the backed-up filesystem.
This.
My working versions and first backups are btrfs. My secondary backups
are reiserfs (my old filesystem of choice, which has been very reliable
for me), just in case both the btrfs versions bite the dust due to a bug
in btrfs itself.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: btrfs send and an existing backup
2014-11-20 14:10 ` Duncan
@ 2014-11-21 12:51 ` Austin S Hemmelgarn
0 siblings, 0 replies; 5+ messages in thread
From: Austin S Hemmelgarn @ 2014-11-21 12:51 UTC (permalink / raw)
To: Duncan, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On 2014-11-20 09:10, Duncan wrote:
> Bardur Arantsson posted on Thu, 20 Nov 2014 14:17:52 +0100 as excerpted:
>
>> If you have no other backups, I would really recommend that you *don't*
>> use btrfs for your backup, or at least have a *third* backup which isn't
>> on btrfs -- there are *still* problems with btrfs that can potentially
>> wreck your backup filesystem. (Although it's obviously less likely if
>> the external HDD will only be connected occasionally.)
>>
>> Don't get me wrong, btrfs is becoming more and more stable, but I
>> wouldn't trust it with my *only* backup, especially if also running
>> btrfs on the backed-up filesystem.
>
> This.
>
> My working versions and first backups are btrfs. My secondary backups
> are reiserfs (my old filesystem of choice, which has been very reliable
> for me), just in case both the btrfs versions bite the dust due to a bug
> in btrfs itself.
>
Likewise, except I use compressed, encrypted tarballs stored on both
Amazon S3 and Dropbox.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-11-21 12:51 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-19 15:58 btrfs send and an existing backup Jakob Schürz
2014-11-20 12:05 ` Marc Joliet
2014-11-20 13:17 ` Bardur Arantsson
2014-11-20 14:10 ` Duncan
2014-11-21 12:51 ` Austin S Hemmelgarn
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox