[Borgbackup] [IDEA] Add support for external commands

[Melkor Lord]

On Sun, Oct 2, 2016 at 10:07 AM, Marian Beermann <public at enkore.de> wrote:

What I don't quite understand yet is where borg serve comes into play.
> If I do, e.g. "ssh someone at somewhere false" then the error code is
> propagated to the host and ssh itself exits with it. So no specific
> handling for SSH would be needed, unless I'm overlooking something here.
>

Isn't the job of "borg serve" to perform the backup itself on the remote
host and just feed back "borg create" (the caller) with
backed-up-data-ready-for-storage? Or do I not understand clearly the
purpose of "borg serve"?

This way, the strain is put on the hosts executing "borg serve", thus
allowing the backup server "borg create" to perform parallel backups (on
different repos of course) without hogging the CPU.

That's why I was thinking this is a job for "borg serve". Another benefit :
When "borg serve" executes the command but it "fails" (non-zero returncode
or --skip-cmd-fail=1,2,n... ) it can "notify" the caller (borg create) to
not create the backup in the first place instead of creating one and then
rollback. I bet this is quite I/O costly on already big repos.

-- 
Unix _IS_ user friendly, it's just selective about who its friends are.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20161002/6edf9edd/attachment.html>