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

Tue Dec 26 23:18:19 GMT 2006

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

Hi Guys

An alternative to sshfs would to to use rsync as has been discussed many
times to backup the bbstored store. This has the benefit of partial /
resumable transfers and has been tested successfully with box.

(Rsync can be configured to run in the foreground if I remember correctly.)

BTW Merry xmas and other such things.
Thank you all for your hardwork this year. I am eagerly awaiting the next
release of box with all it's enhancements.

On 27/12/06, Chris Wilson <chris at 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 at fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup-dev
>

-- 
Thank you.

Scott McNee
Manager

M : 0415 10 44 10
T : 07 3274 3933
E : scott at bizebox.com.au

"backing up your business"
http://www.bizebox.com.au

DISCLAIMER
This transmission is confidential and intended for the addressee only. If
you have received it in error, please delete it and notify the sender.
Unless explicitly attributed, the opinions expressed in this E-mail are
those of the author only and do not represent the official view of bizEbox.
bizEbox checks all inbound/outbound e-mail for Viruses. However, we advise
that this e-mail and any attached files should be re-scanned to detect
viruses. bizEbox accepts no liability for loss or damage (whether caused by
negligence or not) resulting from the use of this or any attached files.

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

Hi Guys An alternative to sshfs would to to use rsync as has been discussed many times to backup the bbstored store. This has the benefit of partial / resumable transfers and has been tested successfully with box. 
 (Rsync can be configured to run in the foreground if I remember correctly.) BTW Merry xmas and other such things. Thank you all for your hardwork this year. I am eagerly awaiting the next release of box with all it's enhancements.
 <div>On 27/12/06, Chris Wilson <<a href="mailto:chris at qwirx.com">chris at qwirx.com</a>> 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: > 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 
<a href="http://qwirx.com">qwirx.com</a>> - 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 at fluffy.co.uk">Boxbackup-dev at 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> -- Thank you. Scott McNee Manager M : 0415 10 44 10 T : 07 3274 3933 E : <a href="mailto:scott at bizebox.com.au">scott at bizebox.com.au</a> 
"backing up your business" <a href="http://www.bizebox.com.au">http://www.bizebox.com.au</a> DISCLAIMER This transmission is confidential and intended for the addressee only. If you have received it in error, please delete it and notify the sender. Unless explicitly attributed, the opinions expressed in this E-mail are those of the author only and do not represent the official view of bizEbox. bizEbox checks all inbound/outbound e-mail for Viruses. However, we advise that this e-mail and any attached files should be re-scanned to detect viruses. bizEbox accepts no liability for loss or damage (whether caused by negligence or not) resulting from the use of this or any attached files.

------=_Part_68708_2816753.1167175099163--