From: "Felix E. Klee" <felix.klee@inka.de>
To: xfs@oss.sgi.com
Subject: Restoring damaged incremental XFS dump?
Date: Mon, 11 Feb 2008 23:39:11 +0100 [thread overview]
Message-ID: <1202769551.16458.1236311973@webmail.messagingengine.com> (raw)
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.
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?
--
Dipl.-Phys. Felix E. Klee
Naunynstr. 2, 76530 Baden-Baden, Germany
Tel.: +49 7221 396961, Fax: +49 7221 396960, Mobile: +49 174 1386060
http://www.linkedin.com/in/feklee
next reply other threads:[~2008-02-11 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 22:39 Felix E. Klee [this message]
2008-02-12 0:03 ` Restoring damaged incremental XFS dump? Timothy Shimmin
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=1202769551.16458.1236311973@webmail.messagingengine.com \
--to=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