[Box Backup] Observations on Win32 client

[Ben Summers]

On 15 Feb 2005, at 12:34, Jamie Neil wrote:

> Hi,
>
> Firstly, thanks to Ben for developing this project - we've been 
> looking for a decent online backup system for 12 months and Box Backup 
> is the first one to really impress :)
>
> We're doing a bit of testing with a Linux (Debian) server and the 
> Win32 client, and I've had a scan through the mailing list archives, 
> but I still have a couple of questions/comments:
>
> 1) Is the native win32 client code going to be merged with the main 
> branch?

Yes.

>  If so, is there any timescale for this?

As soon as I get time to do so!

>  If not, is the source available?

I'm sure Nick will be more than happy to share.

>
> 2) I understand that there is currently a problem with using 
> bbackupctl under Win32 related to sockets. Is anyone working on a fix?

I believe so.

>
> 3) File timestamps seem to be stored correctly (at least the query 
> tool reports them correctly), but not restored. I assume this is a 
> bug.

Sounds like it.

>
> 4) Is anyone actively working on a Win32 GUI interface? If so I would 
> be very interested in helping out - even if it's just testing and 
> debugging (I'm more of a hacker than a programmer). My wishlist for 
> such an interface would be:

A couple of people have mentioned that they're starting such projects 
on the list. I intend for the Box Backup project to remain as a core 
engine with no GUI, but work with others to put a nice front end on it 
(as separate projects).


> 5) The ability to backup and restore ACLs and DOS flags would be nice, 
> but I gather from reading around that this is a much more complex 
> problem that it appears.

I don't think it's too bad, it's just it's a bit fiddly. Locked files 
are more of an issue.

>
> 6) From our testing, boxbackup seems to be able to saturate even fat 
> pipes, which can cause problems when backups are done during the day. 
> Some kind of scheduled bandwidth throttling would be invaluable (I 
> know this could probably be done with another program in true *nix 
> tradition, but in Windows environments this is not so simple).

It's on my list. However, I suggest dealing with it using pf style 
tools or on the firewall/router for now.

Ben