Bacula-users

Re: [Bacula-users] continuing a failed job

2010-01-07 09:09:12
Subject: Re: [Bacula-users] continuing a failed job
From: Phil Stracchino <alaric AT metrocast DOT net>
To: Silver Salonen <silver AT ultrasoft DOT ee>
Date: Thu, 07 Jan 2010 09:06:50 -0500
Silver Salonen wrote:
> On Thursday 07 January 2010 15:41:15 Phil Stracchino wrote:
>> Thus, rsync *is* an option.
> 
> Well, if I plan to use it along with Bacula, a client needs another amount of 
> data-space in a backup-server (and a chroot'ed user for rsync) - user would 
> then rsync his data into the server and Bacula would back it up every night, 
> right? Sounds complicated for a wider use.

A little more complicated, but which is better:  A slightly more
complicated (to set up in the first place) solution that works, and - as
far as I can tell from the page I linked - works without any user action
required once set up; or a solution that's simpler to set up, but
requires a manual user action, and demonstrably doesn't work?

Any system that works beats one which demonstrably doesn't.  Your
client's network connection is demonstrably not stable enough to use
Bacula directly.  Bacula itself is not designed to work around a
connection that unstable.  The rsync protocol is, and Bacula will
happily and reliably back up the rsync'd local mirror.


> I still think that if there was a way for marking a failed job as successful, 
> it would be just about enough.

I think I can safely say that this will never be a Bacula feature, and
nor should it.  If you create the capability to mark failed backups as
successful, you can no longer trust your backups, because you can never
know for sure that any set of backups which contains one or more jobs
which failed, but were then marked as successful, actually contains ANY
complete and consistent image of the filesystem.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users