From: Dave Chinner <david@fromorbit.com>
To: Stevie Trujillo <stevie.trujillo@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump questions
Date: Tue, 23 Dec 2014 07:43:25 +1100 [thread overview]
Message-ID: <20141222204325.GJ24183@dastard> (raw)
In-Reply-To: <20141219095738.6b6e6c88@localhost>
On Fri, Dec 19, 2014 at 09:57:38AM +0100, Stevie Trujillo wrote:
> Hello!
>
> Is xfsdump an ancient relic or something recommended to new users (I
> have never seen anyone recommending it)? I gave it a try and found the
> incremental backups to be really fast!
Still supported, still works, still used in production by lots of
people.
> How are incremental backups implemented? I saw that my inventory file
> is really small. Does it use some internal xfs metadata to detect
> changes? Is it resilient against all kinda renames and changing
> timestamps etc that a user might do? (I've previously used a backup
> system that broke when doing stuff like that)
It should detect renames and changing timestamps, etc. without any
problems.
> Is it possible to backup (and restore) ctimes?
No.
> I read that the incremental backups are limited to a depth of 10. Are
> they intended to be used in a binary tree like fashion?
In theory. Not sure anyone actually uses incremental dumps like that
though, so you'd need to do a bunch of testing before deploying such
a solution.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-12-22 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 8:57 xfsdump questions Stevie Trujillo
2014-12-22 20:43 ` Dave Chinner [this message]
2014-12-23 0:13 ` Stevie Trujillo
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=20141222204325.GJ24183@dastard \
--to=david@fromorbit.com \
--cc=stevie.trujillo@gmail.com \
--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