From: BJ Quinn <bj@placs.net>
To: Chris Mason <chris.mason@oracle.com>
Cc: Jan Schmidt <list.btrfs@jan-o-sch.net>,
Phillip Susi <psusi@cfl.rr.com>, Freddie Cash <fjwcash@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Cloning a Btrfs partition
Date: Thu, 08 Dec 2011 14:38:20 -0600 (CST) [thread overview]
Message-ID: <6d560453-f847-4c7f-a881-ddcdb4e62002@mail.placs.net> (raw)
In-Reply-To: <20111208200524.GT8971@shiny>
> Care to share you rsync script?
Sure. It's a little raw, and makes some assumptions about my environment, but it does the job other than the fact that it takes weeks to run. :)
In the below example, the "main" or source FS is mounted at "/mnt/btrfs", the "backup" or target FS at "/mnt/btrfsbackup", and this script is located at "/mnt/btrfs/backupscripts". I also run a slight variation of this script that makes it only "catch up" on snapshots that don't already exist on the backup FS simply by commenting out the rsync command directly above the echo that says "Export resynced snapshot". If you don't comment that out, then the script attempts to re-sync ALL snapshots, even ones that have already been copied over in a previous run, effectively double checking that everything has already been copied.
This script is as efficient as I know how to make it, as it uses the --no-whole-file and --inplace rsync switches to prevent btrfs from thinking lots of blocks have changed that haven't really changed and eating up lots of space.
Also, an assumption is made that directly under /mnt/btrfs there are many subvolumes, and that the snapshots for these subvolumes are stored under /mnt/btrfs/snapshots/[subvol name]/[snap name].
Lastly, please note that I *DO* understand the purpose of the --bwlimit switch for rsync. I've run it without that and it still takes weeks. It's only in there now because it seemed to prevent issues I was having where the whole system would lock up under heavy btrfs activity. I can't remember if that was a problem I solved by switching out my SATA controller card or by upgrading my kernel, but I don't believe I'm having that issue anymore.
FWIW.
#!/bin/bash
# The following script is for exporting snapshots from one drive to another.
# Putting the word "STOP" (all caps, without quotes) in stopexport.txt will abort
# the process at the end of the current rsync job.
DATE=`date +%Y%m%d`
DATETIME=`date +%Y%m%d%H%M%S`
SCRIPTSFOLDER="/mnt/btrfs/backupscripts"
BACKUPFOLDER="/mnt/btrfs"
EXTERNALDRIVE="/mnt/btrfsbackup"
echo "Export Started `date`"
echo
# This will create all the snapshots in the original drive's snapshots folder
# on the export drive that don't exist on the export drive.
for PATHNAME in $BACKUPFOLDER/snapshots/*
do
if [ `cat $SCRIPTSFOLDER/stopexport.txt` = "STOP" ]; then
echo "STOP"
break
fi
SHARENAME=`basename $PATHNAME`
btrfs subvolume create $EXTERNALDRIVE/$SHARENAME
for SNAPPATH in $PATHNAME/*
do
echo $SNAPPATH
SNAPNAME=`basename $SNAPPATH`
if [ ! -d "$EXTERNALDRIVE/snapshots/$SHARENAME/$SNAPNAME" ]; then
rsync -avvP --delete --bwlimit=20000 --ignore-errors --no-whole-file --inplace $SNAPPATH/ $EXTERNALDRIVE/$SHARENAME
mkdir -p $EXTERNALDRIVE/snapshots/$SHARENAME
btrfs subvolume snapshot $EXTERNALDRIVE/$SHARENAME $EXTERNALDRIVE/snapshots/$SHARENAME/$SNAPNAME
echo "Export created snapshot $EXTERNALDRIVE/snapshots/$SHARENAME/$SNAPNAME"
else
rsync -avvP --delete --bwlimit=20000 --ignore-errors --no-whole-file --inplace $SNAPPATH/ $EXTERNALDRIVE/snapshots/$SHARENAME/$SNAPNAME
echo "Export resynced snapshot $EXTERNALDRIVE/snapshots/$SHARENAME/$SNAPNAME"
fi
if [ `cat $SCRIPTSFOLDER/stopexport.txt` = "STOP" ]; then
echo "STOP"
break
fi
done;
done;
echo "Export Completed `date`"
next prev parent reply other threads:[~2011-12-08 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bb747e0c-d6d8-4f60-a3f6-cf64c856515e@mail.placs.net>
2011-12-07 18:35 ` Cloning a Btrfs partition BJ Quinn
2011-12-07 18:39 ` Freddie Cash
2011-12-07 18:49 ` BJ Quinn
2011-12-08 15:49 ` Phillip Susi
2011-12-08 16:07 ` BJ Quinn
2011-12-08 16:09 ` Jan Schmidt
2011-12-08 16:28 ` BJ Quinn
2011-12-08 16:41 ` Jan Schmidt
2011-12-08 19:56 ` BJ Quinn
2011-12-08 20:05 ` Chris Mason
2011-12-08 20:38 ` BJ Quinn [this message]
2011-12-12 21:41 ` BJ Quinn
2011-12-13 22:06 ` Goffredo Baroncelli
2011-12-30 0:25 ` BJ Quinn
2012-01-12 0:52 ` BJ Quinn
2012-01-12 6:41 ` Chris Samuel
2011-12-08 16:27 ` Stephane CHAZELAS
2011-12-08 10:00 ` Stephane CHAZELAS
2011-12-08 19:22 ` Goffredo Baroncelli
2013-07-29 8:21 Fwd: " Jan Schmidt
2013-07-29 15:32 ` BJ Quinn
2013-07-30 10:28 ` Jan Schmidt
2013-08-19 20:45 ` BJ Quinn
2013-08-20 9:59 ` Xavier Bassery
2013-08-20 15:43 ` BJ Quinn
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=6d560453-f847-4c7f-a881-ddcdb4e62002@mail.placs.net \
--to=bj@placs.net \
--cc=chris.mason@oracle.com \
--cc=fjwcash@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=psusi@cfl.rr.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;
as well as URLs for NNTP newsgroup(s).