All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Hart" <jfhart085@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: backing up a file server with many subvolumes
Date: Sat, 25 Mar 2017 23:00:20 -0400	[thread overview]
Message-ID: <58D72EC4.9020101@gmail.com> (raw)

I have a Btrfs filesystem on a backup server.  This filesystem has a 
directory to hold backups for filesystems from remote machines.  In this 
directory is a subdirectory for each machine.  Under each machine 
subdirectory is one directory for each filesystem (ex /boot, /home, etc) 
on that machine.  In each filesystem subdirectory are incremental 
snapshot subvolumes for that filesystem.  The scheme is something like 
this:

<top>/backup/<machine>/<filesystem>/<many snapshot subvolumes>

I'd like to try to back up (duplicate) the file server filesystem 
containing these snapshot subvolumes for each remote machine.  The 
problem is that I don't think I can use send/receive to do this. "Btrfs 
send" requires "read-only" snapshots, and snapshots are not recursive as 
yet.  I think there are too many subvolumes which change too often to 
make doing this without recursion practical.

Any thoughts would be most appreciated.

J. Hart


             reply	other threads:[~2017-03-26  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26  3:00 J. Hart [this message]
2017-03-26  9:14 ` backing up a file server with many subvolumes Roman Mamedov
2017-03-26 19:51   ` Adam Borowski
2017-03-26 20:24 ` Peter Grandi
2017-03-27  5:57 ` Marat Khalili
2017-03-27 12:00   ` J. Hart
2017-03-27 13:05     ` Graham Cobb
2017-04-01  8:24   ` Kai Krakow
2017-03-27 11:53 ` Austin S. Hemmelgarn
2017-04-01  8:21   ` Kai Krakow

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=58D72EC4.9020101@gmail.com \
    --to=jfhart085@gmail.com \
    --cc=linux-btrfs@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.