Marc MERLIN posted on Thu, 20 Mar 2014 22:57:33 -0700 as excerpted:
On Sun, Mar 16, 2014 at 10:42:24PM -0700, Marc MERLIN wrote:
On Thu, Mar 06, 2014 at 09:33:24PM +, Duncan wrote:
However, best snapshot management practice does progressive snapshot
thinning, so you never have more than
On Sun, Mar 16, 2014 at 10:42:24PM -0700, Marc MERLIN wrote:
On Thu, Mar 06, 2014 at 09:33:24PM +, Duncan wrote:
However, best snapshot management practice does progressive snapshot
thinning, so you never have more than a few hundred snapshots to manage
at once. Think of it this way.
On Sun, 9 Mar 2014 03:30:44 PM Duncan wrote:
While I realize that was in reference to the up in flames comment and
presumably if there's a need to worry about that, offsite backup /is/ of
some value, for some people, offsite backup really isn't that valuable.
Actually I missed that comment
On Mar 7, 2014, at 7:03 AM, Eric Mesa ericsbinarywo...@gmail.com wrote:
Duncan - thanks for this comprehensive explanation. For a huge portion of
your reply...I was all wondering why you and others were saying snapshots
aren't backups. They certainly SEEMED like backups. But now I see that
Chris Samuel posted on Sun, 09 Mar 2014 15:13:42 +1100 as excerpted:
On Fri, 7 Mar 2014 04:14:16 PM Sander wrote:
But if the filesystem or underlaying disk goes up in flames, the
snapshots are toast as well. So you need additional backups, preferably
not on the same hardware, for real
Wolfgang Mader posted on Fri, 07 Mar 2014 11:13:51 +0100 as excerpted:
Duncan, thank you for this comprehensive post. Really helpful as always!
[...]
As for restoring, since a snapshot is a copy of the filesystem as it
existed at that point, and the method btrfs exposes for accessing them
Eric Mesa posted on Fri, 07 Mar 2014 14:03:44 + as excerpted:
Duncan - thanks for this comprehensive explanation. For a huge portion
of your reply...I was all wondering why you and others were saying
snapshots aren't backups. They certainly SEEMED like backups. But now I
see that the
On Fri, 7 Mar 2014 04:14:16 PM Sander wrote:
But if the filesystem or underlaying disk goes up in flames, the
snapshots are toast as well. So you need additional backups,
preferably not on the same hardware, for real protection against
data loss.
...and don't forget to think about off-site
Duncan, thank you for this comprehensive post. Really helpful as always!
[...]
As for restoring, since a snapshot is a copy of the filesystem as it
existed at that point, and the method btrfs exposes for accessing them is
to mount that specific snapshot, to restore an individual file from a
Duncan 1i5t5.duncan at cox.net writes:
*But*, btrfs snapshots by themselves remain on the existing btrfs
filesystem, and thus are subject to many of the same risks as the
filesystem itself. As you mentioned raid is redundancy not backup,
snapshots aren't backup either; snapshots are
Eric Mesa wrote (ao):
Duncan - thanks for this comprehensive explanation. For a huge portion of
your reply...I was all wondering why you and others were saying snapshots
aren't backups. They certainly SEEMED like backups. But now I see that the
problem is one of precise terminology vs
apologies if this is a resend - it appeared to me that it was rejected
because of something in how Gmail was formatting the message. I can't find
it in the Gmane archives which leads me to believe it was never delivered.
I was hoping to gain some clarification on btrfs snapshops and how they
Brian Wong wrote: a snapshot is different than a backup, with a snapshot
you're still accessing a read-only version of the live filesystem. i don't
know the specifics of btrfs but if you take daily snapshots, you should be
able to restore a single file from the five-days-ago snapshot by browsing
Brian Wong wrote: a snapshot is different than a backup, with a snapshot
you're still accessing a read-only version of the live filesystem. i don't
know the specifics of btrfs but if you take daily snapshots, you should be
able to restore a single file from the five-days-ago snapshot by browsing
On 2014/03/06 09:27 PM, Eric Mesa wrote:
Brian Wong wrote: a snapshot is different than a backup
[snip]
...
Three hard drives: A, B, and C.
Hard drives A and B - btrfs RAID-1 so that if one drive dies I can keep
using my system until the replacement for the raid arrives.
Hard drive C - gets
Eric Mesa posted on Thu, 06 Mar 2014 18:18:15 + as excerpted:
apologies if this is a resend - it appeared to me that it was rejected
because of something in how Gmail was formatting the message. I can't
find it in the Gmane archives which leads me to believe it was never
delivered.
Hi,
I have a local btrfs file system with various sub-volumes that have
had snapshots done on them.
Is there some tool like rsync that I could copy all the data and
snapshots to a backup system, but still only use the same amount of
space as the source filesystem.
I see a problem being getting a
On Mon, Mar 26, 2012 at 3:56 PM, Felix Blanke felixbla...@gmail.com wrote:
On 3/26/12 10:30 AM, James Courtier-Dutton wrote:
Is there some tool like rsync that I could copy all the data and
snapshots to a backup system, but still only use the same amount of
space as the source filesystem.
Fajar A. Nugraha posted on Mon, 26 Mar 2012 16:01:54 +0700 as excerpted:
On Mon, Mar 26, 2012 at 3:56 PM, Felix Blanke felixbla...@gmail.com
wrote:
On 3/26/12 10:30 AM, James Courtier-Dutton wrote:
Is there some tool like rsync that I could copy all the data and
snapshots to a backup system,
On Mon, Mar 26, 2012 at 4:26 PM, Duncan 1i5t5.dun...@cox.net wrote:
Fajar A. Nugraha posted on Mon, 26 Mar 2012 16:01:54 +0700 as excerpted:
On Mon, Mar 26, 2012 at 3:56 PM, Felix Blanke felixbla...@gmail.com
wrote:
On 3/26/12 10:30 AM, James Courtier-Dutton wrote:
Is there some tool like
20 matches
Mail list logo
