linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano ES <lucmove@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Questions about backups with XFS
Date: Sat, 7 Oct 2017 11:43:43 -0300	[thread overview]
Message-ID: <20171007114343.3bd42f98@lubh.lubhome> (raw)

I have a few questions and I was torn between asking them separately 
and putting them all in one message. I decided for the latter and I 
hope this is not a problem.

Once upon a time, many many years ago, I used to make backup copies 
of my file systems with the 'cp -aux' command, including my live 
root file system. Luckily, I never had to restore any live root file 
system from those backups. They probably would never have worked.

Later on, someone taught me to do it like this:

find /source -xdev -print0 | cpio -pa0V /target

That command is supposed to copy everything, including special files 
(not really sure which) that mere cp or even rsync would not copy. 
I actually used that approach several times, including restoration, 
and it always worked.

For some reason, I stopped making backups of my live root file 
system, but I still backup other partitions with rsync, always with 
the --delete-before parameter, so the target is always an exact copy 
of the source.

I have been using XFS for a few years and thought that maybe it's 
time I enjoyed all the benefits of the XFS management tools.
However, I am uncertain about things I haven't been able to find in 
the documentation or even on the Web:

Question #1:
Does xfsdump really copy EVERYTHING? Can I backup a full live root 
file system with it and expect a restored copy to boot and run 
uneventfully? Or should I rather do a 'hard' image with xfs_copy? 

Question #2:
By the way, I see that pcmanfm can mount an xfs_copy image quite 
easily, but how do I mount it on the command line, and can I mount 
it in rw mode?

Question #3:
If I make incremental backups with several levels then perform a 
restore, I know that files added in subsequent levels will be added 
to the dump, but what happens with files that have been deleted in 
the source file system? Will they be removed from the dump? In other 
words, is there something analogous to rsync's --delete-before in 
xfsdump/xfsrestore?

Question #4:
Is there any benefit to making incremental backups of a small file 
system? I mean, it's just 10GB, and deleting the old backup and 
doing a level 0 dump from scratch would take what, 3 minutes.

Please note that my goal is disaster recovery. I am planning to run 
a few experiments on my live root file and must be able to restore 
it to a certain state whenever necessary.


Thanks in advance,

-- 
Luciano ES
>>

             reply	other threads:[~2017-10-07 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-07 14:43 Luciano ES [this message]
2017-10-09  8:44 ` Questions about backups with XFS Carlos Maiolino
2017-10-09 10:57   ` Dave Chinner
2017-10-12  1:03     ` Luciano ES
2017-10-09 15:08   ` Carlos E. R.
2017-10-12  0:58   ` Luciano ES
2017-10-12  5:13     ` Keith Keller
2017-11-06  3:29 ` Supposedly identical file system wastes space Carlos E. R.
2017-11-06  6:19 ` Dave 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=20171007114343.3bd42f98@lubh.lubhome \
    --to=lucmove@gmail.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).