Re: [rdiff-backup-users] Clarification of --restrict-update-only

[Chris G]

On Wed, Feb 04, 2009 at 08:32:07PM -0500, Dimi Paun wrote:
> 
> On Thu, 2009-02-05 at 01:52 +0100, Jakob Unterwurzacher wrote:
> > IMO "the" solution to this is to use pull-style backups. The backup
> > machine should login to your machine (and not the other way round) and
> > start the backup.
> 
> That's right -- this is the model we use in safekeep too 
> (plug http://safekeep.sf.net). It also has the added advantage
> of nicely centralizing all settings, in effect making the
> machines that are being backed-up stateless from a configuration
> perspective.
> 
Stateless except that they need some way of telling their owner that
the backup has failed.  In my small LAN situation the backup server
runs unattended in the garage, my desktop machine runs all the time
and other desktop machine are turned on as required.

I *need* to know if the backups to the machine in the garage have
failed, I'm not disciplined enough to check manually if the machine
is running every day.  Backups can fail if the cable gets
disconnected, if the machine dies/loses power, or if the software
screws up.  A 'push' backup gives me a pretty foolproof way of
checking that does nothing if all is well and sends me a mail message
if it's gone wrong.

-- 
Chris Green