linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Dormann <wdormann@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Silent skipping of file during xfsrestore
Date: Mon, 28 Nov 2016 17:00:29 -0500	[thread overview]
Message-ID: <3c5d290e-c960-bf5e-ee38-1ece24c6d929@gmail.com> (raw)
In-Reply-To: <20161128213350.GB28177@dastard>

On 11/28/16 4:33 PM, Dave Chinner wrote:
> On Mon, Nov 28, 2016 at 08:17:00AM -0500, Will Dormann wrote:
>> If this isn't possible, then I suspect that an xfsdump/xfsrestore of a
>> (running?) system perhaps isn't as robust as I had hoped. 
> 
> It has never been 100% robust when run on a live filesystem that is
> being modified as the backup is running. If you want robust, exact
> point in time backups, then snapshot the filesystem and run the
> backup from the snapshot. Then remove the snapshot once the backup
> completes....


Good to know!  In the past I had done offline backups, but I had
eventually figured that xfsdump + mysqldump might get me what I want
without rebooting.

Given that I don't have any LVM to provide snapshots, the best bet may
be to have an offline backup for guaranteed, bare-metal restores.  And
xfsdump/mysqldump for more-handy online backups / restores.


Thanks for the help.


-WD

  reply	other threads:[~2016-11-28 22:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  1:49 Silent skipping of file during xfsrestore Will Dormann
2016-11-28  1:59 ` Dave Chinner
2016-11-28  5:00   ` Will Dormann
2016-11-28  8:21     ` Dave Chinner
2016-11-28 13:17       ` Will Dormann
2016-11-28 21:33         ` Dave Chinner
2016-11-28 22:00           ` Will Dormann [this message]
2016-11-28 16:10       ` Will Dormann
2016-11-28 16:32         ` Eric Sandeen
2016-11-28 16:43           ` Will Dormann
2016-11-28 17:45             ` Eric Sandeen

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=3c5d290e-c960-bf5e-ee38-1ece24c6d929@gmail.com \
    --to=wdormann@gmail.com \
    --cc=david@fromorbit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).