From: Gionatan Danti <g.danti@assyoma.it>
To: linux-xfs@vger.kernel.org
Cc: g.danti@assyoma.it
Subject: xfs_metadump as a backup tool
Date: Mon, 21 Aug 2017 21:59:01 +0200 [thread overview]
Message-ID: <c8f366449091c278310acb5fbb13a11f@assyoma.it> (raw)
Hi all,
I wish to ask if someone is using xfs_metadump as a "real" backup tool -
ie: in production.
I was wondering how to lower recovery time in case of filesystem
corruption, and the idea of using xfs_metadump + xfs_mdrestore struck
me.
I plan to have a single, relatively big XFS volume with an handfull of
fully preallocated large files (VM disk images). Basically, I was
thinking about:
- take a LVM snapshot;
- mount the snap volume as read-only;
- copy the user data (via tar/rsync/whatever);
- additionally, xfs_metadump its metadata content.
If a major filesystem corruption occour, as a first step I should be
able to simply restore its metadata with xfs_mdrestore and re-gain
access to files/data blocks. A potential pitfall would be related to
extents that at the time of xfs_metadump where marked as "unwritten" but
later were written - restoring the old metadata will immediately turn
user data into zeroes. It is possible to fully allocate a file *without*
marking the allocated extents as "unwritten"? Yes, I know this has
security implications...
Is this a good idea? I am missing something?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next reply other threads:[~2017-08-21 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:59 Gionatan Danti [this message]
2017-08-21 20:11 ` xfs_metadump as a backup tool Eric Sandeen
2017-08-22 6:11 ` Gionatan Danti
2017-08-22 6:11 ` Gionatan Danti
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=c8f366449091c278310acb5fbb13a11f@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.