public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: weber@zbfmail.de
Cc: Xfs <xfs@oss.sgi.com>
Subject: Re: a maybe silly question about xfsdump
Date: Wed, 21 May 2014 07:07:32 +1000	[thread overview]
Message-ID: <20140520210732.GI8554@dastard> (raw)
In-Reply-To: <33dfdd6d469a5be58f79cbf0f0222c51@zbfmail.de>

On Tue, May 20, 2014 at 05:33:15PM +0200, Marko Weber|8000 wrote:
> 
> hello, again me ;-)
> 
> i use at runtime this command to backup root partition of a server:
> 
> xfsdump -f /var/backup/root2.dump -l 0 -p 5 -L rootdump -M rootdump /
> 
> 
> i googled around alot, cause a question wont get out of my mind:
> is this backup consistent?
> And what about consistency when i backup a mysql partition at runtime?

First, define consistent....

If you define consistent as a point in time snapshot where
everything is from the same point in time, then xfsdump does not
provide you with that. You need to quiese mysql and snapshot the
filesystem, then backup the snapshot to get a consistent point in
time backup of the filesytem from the application data all the way
down to the filesystem metadata.

That's no different to any other backup process - even if you are
using btrfs you still need to quiesce the application to get a
consistent snapshot of the application data in the filesystem
snapshot that you are backing up....

> but my most wondering is abot this:
> 
> bunka ~ # df -h
> Filesystem                     Size  Used Avail Use% Mounted on
> /dev/root                      135G   11G  125G   8% /
> 
> 
> but the saved dump shows:
> 
> 
> bunka ~ # ls -lh /var/backup/
> 
> -rw-r--r-- 1 root root 8.4G May 20 17:29 root2.dump

xfsdump stores information in a more compact form than the
filesystem does on disk. It doesn't need all the metadata the
filesystem has on disk to reference all the data you are backing
up...

Also, they may be some files maked as "no dump" that will be
skipped, and other files that (e.g. iopen, unlinked tmpfiles) can't
be found via a directory traversal and so aren't backed up.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2014-05-20 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 15:33 a maybe silly question about xfsdump Marko Weber|8000
2014-05-20 21:07 ` Dave Chinner [this message]

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=20140520210732.GI8554@dastard \
    --to=david@fromorbit.com \
    --cc=weber@zbfmail.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