[Box Backup-dev] Using box-backup without daemon, via a remote shell (like rsync)

Tue, 26 Dec 2006 21:05:00 +0200

------=_Part_86479_12847168.1167159900203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks for the suggestions.
I managed to connect to the server (box-backup server listening on localhost
instead of the public interface of the server):

I ran in Cygwin:

ssh -L 2201:localhost:2201 user@server.com

Then I ran in the connected shell:

bbstored bbstored.conf SINGLEPROCESS

Then I connected the client to localhost:2201.

I could now write a script to automate this process.

Now the only problem is that I don't know how to stop the bbstored started
in SINGLEPROCESS mode.
Is it OK to use a Ctrl-C ? Can something bad happen if you interrupt it like
this while the server is doing some processing ? Are signals handled ?

I'll also try the sshfs way.

Thanks,
Andrei

On 12/26/06, Chris Wilson <chris@qwirx.com> wrote:
>
> Hi Martin,
>
> On Tue, 26 Dec 2006, Martin Ebourne wrote:
> > On Tue, 2006-12-26 at 14:27 +0200, Andrei wrote:
> >> I think it would be useful if the box-backup client could connect to a
> >> linux server via a standard ssh connection on port 22 (using linux
> >> username and password), and then communicate with the box-backup
> >> server via pipes (so no network connections will be involved).
> >>
> >> This would help using box-backup on servers that do not allow
> >> listening daemons or persistent processes but do allow connecting
> >> through ssh. The box-backup server maintenance could be executed
> >> manually through a cronjob.
> >
> > You can do this using ssh port forwarding already, although that is
> > obviously a bit of work to set up.
>
> Unfortunately that doesn't work if daemons are not allowed on the remote
> host. Although you could start the store daemon when the backup starts and
> kill it afterwards.
>
> Another way might be to mount the remote storage box using sshfs on the
> client, and run the store and backup daemons on the client.
>
> Cheers, Chris.
> --
> _ ___ __     _
>   / __/ / ,__(_)_  | Chris Wilson <0000 at qwirx.com> - Cambs UK |
> / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer |
> \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software |
> _______________________________________________
> Boxbackup-dev mailing list
> Boxbackup-dev@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev
>

------=_Part_86479_12847168.1167159900203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks for the suggestions.<br>I managed to connect to the server (box-backup server listening on localhost instead of the public interface of the server):<br><br>I ran in Cygwin:<br><br>ssh -L 2201:localhost:2201 <a href="mailto:user@server.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">

user@server.com</a><br><br>Then I ran in the connected shell:<br><br>bbstored bbstored.conf SINGLEPROCESS<br><br>Then I connected the client to localhost:2201.<br><br>I could now write a script to automate this process.<br>

Now the only problem is that I don&#39;t know how to stop the bbstored started in SINGLEPROCESS mode. Is
it OK to use a Ctrl-C ? Can something bad happen if you interrupt it
like this while the server is doing some processing ? Are signals
handled ?
 I&#39;ll also try the sshfs way. Thanks, Andrei <div>On 12/26/06, Chris Wilson &lt;<a href="mailto:chris@qwirx.com">
chris@qwirx.com</a>&gt; wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Martin, On Tue, 26 Dec 2006, Martin Ebourne wrote:
 &gt; On Tue, 2006-12-26 at 14:27 +0200, Andrei wrote: &gt;&gt; I think it would be useful if the box-backup client could connect to a &gt;&gt; linux server via a standard ssh connection on port 22 (using linux 
&gt;&gt; username and password), and then communicate with the box-backup &gt;&gt; server via pipes (so no network connections will be involved). &gt;&gt; &gt;&gt; This would help using box-backup on servers that do not allow
 &gt;&gt; listening daemons or persistent processes but do allow connecting &gt;&gt; through ssh. The box-backup server maintenance could be executed &gt;&gt; manually through a cronjob. &gt; &gt; You can do this using ssh port forwarding already, although that is
 &gt; obviously a bit of work to set up. Unfortunately that doesn&#39;t work if daemons are not allowed on the remote host. Although you could start the store daemon when the backup starts and kill it afterwards.
 Another way might be to mount the remote storage box using sshfs on the client, and run the store and backup daemons on the client. Cheers, Chris. -- _ ___ __&nbsp;&nbsp;&nbsp;&nbsp; _ &nbsp;&nbsp;/ __/ / ,__(_)_&nbsp;&nbsp;| Chris Wilson &lt;0000 at 
<a href="http://qwirx.com">qwirx.com</a>&gt; - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | _______________________________________________
 Boxbackup-dev mailing list <a href="mailto:Boxbackup-dev@fluffy.co.uk">Boxbackup-dev@fluffy.co.uk</a> <a href="http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev">http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev
</a> </blockquote></div>

------=_Part_86479_12847168.1167159900203--