From: Marc MERLIN <marc@merlins.org>
To: Donald Pearson <donaldwhpearson@gmail.com>
Cc: sander@humilis.net, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Anyone tried out btrbk yet?
Date: Wed, 15 Jul 2015 14:48:03 -0700 [thread overview]
Message-ID: <20150715214803.GF5274@merlins.org> (raw)
In-Reply-To: <CAC=t97CxDRoakqzoOAoHpN=1qS1jyvMEfOCe+RWvGTm6xSCqPQ@mail.gmail.com>
On Wed, Jul 15, 2015 at 09:42:28AM -0500, Donald Pearson wrote:
> Implementation question about your scripts Marc..
make sure you Cc me then, I could have missed that Email :)
> I've set up some routines for different backup and retention intervals
> and periods in cron but quickly ran in to stepping on my own toes by
> the locking mechanism. I could just disable the locking but I'm not
> sure if that's the best approach and I don't know what it was
> implemented to prevent in the first place.
Try --postfix servername
it'll add the destination server in the snapshot rotation and the
lockfile.
Otherwise, you can just trivially modify the script to take --lock as an
argument, or you can even
ln -s btrfs-subvolume-backup btrfs-subvolume-backupserver2
and the script will automatically make a /var/run/btrfs-subvolume-backupserver2
as a lockfile.
Hope this helps.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
prev parent reply other threads:[~2015-07-16 0:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 12:26 Anyone tried out btrbk yet? Martin Steigerwald
2015-07-09 17:12 ` Henri Valta
2015-07-09 17:17 ` Marc MERLIN
2015-07-10 1:35 ` Donald Pearson
2015-07-10 1:38 ` Donald Pearson
2015-07-10 4:02 ` Paul Harvey
2015-07-10 10:46 ` Axel Burri
2015-07-12 3:55 ` Marc MERLIN
2015-07-13 0:42 ` Marc MERLIN
2015-07-15 0:03 ` Paul Harvey
2015-07-15 3:14 ` Marc MERLIN
2015-07-15 8:00 ` Sander
2015-07-15 14:42 ` Donald Pearson
2015-07-15 18:02 ` Donald Pearson
2015-07-15 21:49 ` Marc MERLIN
2015-07-20 5:15 ` Donald Pearson
2015-07-20 8:28 ` Duncan
2015-07-20 13:33 ` Donald Pearson
2015-07-21 9:29 ` Duncan
2015-07-22 1:29 ` Donald Pearson
2015-07-25 13:27 ` Donald Pearson
2015-07-26 5:39 ` Duncan
2015-07-15 21:48 ` Marc MERLIN [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=20150715214803.GF5274@merlins.org \
--to=marc@merlins.org \
--cc=donaldwhpearson@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sander@humilis.net \
/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).