public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: "Copy until full" tool
Date: Wed, 18 Jan 2017 03:34:00 -0000	[thread overview]
Message-ID: <CAJ1FpuNcurUd_zWQwdzovPou73-UTgt0n2E01X0pNTg3tX8QOQ@mail.gmail.com> (raw)
In-Reply-To: <6aac2f2a-77e9-43a0-e62c-f7d68b5f9f66@netfence.it>

On 17 January 2017 at 01:57, Andrea Venturoli  wrote:
>
> Hello.
>
> I've got a 2TB backup HD which is filled with several copies (at different times) of the same data; in other words, I could have the following directories:
>
> Data20170117
> Data20170110
> Data20170103
> ...
> Data20161220
> User20170117
> User20170110
> User20170103
> ...
> User20161220
> DB20170117
> DB20170110
> DB20170103
> ...
> DB20161220
>
>
>
> Now I periodically need to copy this HD to another one, which is, alas, only 1TB.
> So I'd like to only transfer the most recent copies, either until the disk is full or by specifying a number of "copies" to keep. Of course the older ones should be deleted.
>
> Think rsync (which I've been using extensibly), but with a size barrier.


This is not specifically a cygwin solution, but I am using it with my
cygwin installation as well as interesting parts of my windows
installation.

Restic is a program that does backups right.

home page: https://restic.github.io/
documentation: https://restic.readthedocs.io/en/latest/
source: https://github.com/restic/restic

Read the home page. I think it meets its design goals very well.

HTH,
Doug


-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2017-01-18  3:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  8:58 Andrea Venturoli
2017-01-18  3:34 ` Doug Henderson [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=CAJ1FpuNcurUd_zWQwdzovPou73-UTgt0n2E01X0pNTg3tX8QOQ@mail.gmail.com \
    --to=djndnbvg@gmail.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).