linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: cancel btrfs delete job
Date: Fri, 27 Jun 2014 05:26:14 +0000 (UTC)	[thread overview]
Message-ID: <pan$207f$e9dab0e9$594ccc79$94281c38@cox.net> (raw)
In-Reply-To: 61052648.lopAtLMs1F@xev

Russell Coker posted on Fri, 27 Jun 2014 10:49:40 +1000 as excerpted:

> On Thu, 26 Jun 2014 13:25:09 Duncan wrote:
>> properly.  And if you do automated snapshots, use a good thinning
>> script to thin them down so you're well under 500. (I've posted figures
>> where even starting with per-minute snapshots, thinning down to 10
>> minute, then to half hour within the day, then to say 4/day after two
>> days, 1/day after a week, one a week after four weeks, one every 13
>> weeks aka quarterly after say six months, and clearing them all and
>> relying on off-
>> machine backups after a year or 18 months, runs only 250-ish or so,
>> under 300.)
> 
> What scripts are people using for this?

I don't do much with snapshots here, and definitely don't do auto-
snapshotting, but snapper's a popular one, there's Marc Merlin's script,
and there's several other related links I've not looked closely at on the
wiki, as well.

The use-cases page has a section on time-machine snapshots, with several
links including snapper:

https://btrfs.wiki.kernel.org/index.php/UseCases#How_can_I_use_btrfs_for_backups.2Ftime-machine.3F

I don't see Marc Merlin's script linked there, but it's linked from the
FAQ, snapshot example section:

https://btrfs.wiki.kernel.org/index.php/FAQ#snapshot_example

(Someone with a wiki login could probably add Marc's script to the use-
cases list, and then reword the FAQ entry appropriately and point it to
the use-cases discussion instead of just linking Marc's script.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-06-27  5:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 11:47 cancel btrfs delete job Franziska Näpelt
2014-06-26 13:25 ` Duncan
2014-06-26 13:47   ` Franziska Näpelt
2014-06-27  0:49   ` Russell Coker
2014-06-27  5:26     ` Duncan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-27  5:00 Franziska Näpelt
2014-06-27  5:58 ` Satoru Takeuchi
2014-06-27  8:09   ` Satoru Takeuchi
2014-06-24  7:50 Franziska Näpelt
2014-06-26  7:17 ` Satoru Takeuchi
     [not found]   ` <1403777123.7657.5.camel@hsew-frn.HIPERSCAN>
     [not found]     ` <53AC013E.5000702@jp.fujitsu.com>
2014-06-26 11:34       ` Franziska Näpelt
2014-06-26 23:29         ` Satoru Takeuchi
2014-06-27  8:55           ` Satoru Takeuchi
2014-06-26 11:06 ` Franziska Näpelt
2014-06-26 11:30   ` Duncan

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='pan$207f$e9dab0e9$594ccc79$94281c38@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 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).