[Box Backup-dev] observation with client side cached state
file
Martin Ebourne
boxbackup-dev@fluffy.co.uk
Wed, 26 Jul 2006 14:06:59 +0100
"G." <gniemcew@yahoo.com> wrote:
> I see your point, but should a server store blow up, an admin has no
> way to force a backup from
> all users. Hmmmmmm. I would say let's stick to the old and
> well-proven Linux methodology: when in
> doubt, make it a user option.
No, that's a bad idea in this case. Where there's more than one right
way to do it, make it configurable. Where this is not the case do the
right thing only.
I don't really see the harm in bbackupd always connecting. The amount
of data transfer is minimal and it gives you an early warning if
there's any kind of communication issue. Also reassuring from the
server side that all clients are operational. This was discussed
previously about adding a client heartbeat so the server knows it is
alive.
Cheers,
Martin.