public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: "Felix E. Klee" <felix.klee@inka.de>
Cc: xfs@oss.sgi.com
Subject: Re: Restoring damaged incremental XFS dump?
Date: Tue, 12 Feb 2008 11:03:57 +1100	[thread overview]
Message-ID: <47B0E26D.7070807@sgi.com> (raw)
In-Reply-To: <1202769551.16458.1236311973@webmail.messagingengine.com>

Felix E. Klee wrote:
> I wonder whether I should use xfsdump as a replacement for a more
> traditional incremental backup solution centered around the TAR archiver
> STAR.  The advantage of STAR seems to be that files can also be
> recovered even if, for example, the level 0 dump is damaged.  After all,
> one is dealing with TAR, a pretty transparent archive format. The
> advantage of xfsdump is that it creates true snapshots.
>
I'm not sure what you mean by "true snapshots".
I wouldn't really call it snapshots as in what you could get if you
froze the filesystem etc..
But I presume you are meaning how it tries to store all the xfs
supported information including extended attributes, extended inode attributes,
holes, etc...

> So, what happens when the level 0 dump created with xfsdump becomes
> damaged.  Will I still be able to recover some files?  What about files
> from >0 dumps?
> 
Yes you will still be able to restore stuff.
However, it is in its own format so only xfsrestore will be able to do your
restoring.
Dumps are separated into what it calls media files which are meant to
be self containing. So damage to 1 theoretically shouldn't prevent restoring
from another media file.
Multiple media files are normally only used for tape (only 1 used for a dump
to a file).
And an incremental dump should also be able to be restored in isolation
and there are some QA tests (in xfs-cmds/xfstests) that test this.

--Tim

  reply	other threads:[~2008-02-12  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 22:39 Restoring damaged incremental XFS dump? Felix E. Klee
2008-02-12  0:03 ` Timothy Shimmin [this message]
2008-02-12 11:17   ` Felix E. Klee
2008-02-12 12:24     ` David Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47B0E26D.7070807@sgi.com \
    --to=tes@sgi.com \
    --cc=felix.klee@inka.de \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox