public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Update request for rdiff-backup
Date: Wed, 6 May 2020 07:22:48 -0600	[thread overview]
Message-ID: <2798fa4d-eafb-f246-7f85-bf58a99da14d@SystematicSw.ab.ca> (raw)
In-Reply-To: <9d3b33bf-31c2-6a3f-847a-a85de1cb222d@snkmail.com>

On 2020-05-05 23:23, Cygwin wrote:
>> The ssh, rsync, and most Unix remote access utilities use [[user@]host:]path;
>> and rsync daemon processes and rdiff-backup use [[user]@host::]path specs or
>> URIs; see:
>>
>>     http://rdiff-backup.nongnu.org/rdiff-backup.1.html
>>
>>     https://rdiff-backup.net/docs/examples.html

> Thanks for the suggestion Brian.
> 
> I would prefer to use[[user]@host::]path , but based on my reading of the man
> page and examples, it requires rdiff-backup to be available on the remote server
> which unfortunately is not the case in my situation.

It is impossible to use any rsync, rdiff, or rdiff-backup commands against a
remote server without the corresponding daemon running on that server, as the
commands omit sending as many data blocks as possible by sending block
signatures instead, then on signature mismatch sending the data black and
storing it in the new file copy, an incremental diff, and/or a date-time stamped
backup.

> I don't see anything in the rdiff-backup man page or examples indicating you can
> use URIs.  Can you be more specific about where it shows that?

I would expect it to support specs in the form of rsync URIs, not general URI
schemes as supported by curl or duplicity e.g.

rsync(1):
"	Access via rsync daemon:
         Pull: rsync [OPTION...] [USER@]HOST::SRC... [DEST]
               rsync [OPTION...] rsync://[USER@]HOST[:PORT]/SRC... [DEST]
         Push: rsync [OPTION...] SRC... [USER@]HOST::DEST
               rsync [OPTION...] SRC... rsync://[USER@]HOST[:PORT]/DEST

       Usages with just one SRC arg and no DEST arg will list the source files
instead of copying."

similar to ssh(1):
	"or a URI of the form ssh://[user@]hostname[:port]"

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-05-06 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  6:43 qrasmfu8f4
2020-05-04 17:44 ` David Rothenberger
2020-05-05  4:17   ` Cygwin
2020-05-05  9:37     ` Andrey Repin
2020-05-08  6:15       ` Cygwin
2020-05-08 15:09         ` David Rothenberger
2020-05-05 15:16     ` Brian Inglis
2020-05-06  5:23       ` Cygwin
2020-05-06 13:22         ` Brian Inglis [this message]
2020-05-05 18:38     ` David Rothenberger

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=2798fa4d-eafb-f246-7f85-bf58a99da14d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).