Bacula-users

Re: [Bacula-users] continuing a failed job

2010-01-07 09:16:52
Subject: Re: [Bacula-users] continuing a failed job
From: Silver Salonen <silver AT ultrasoft DOT ee>
To: Phil Stracchino <alaric AT metrocast DOT net>
Date: Thu, 7 Jan 2010 16:14:49 +0200
On Thursday 07 January 2010 16:06:50 Phil Stracchino wrote:
> 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?

Well, my approach can easily be set up without requiring manual user 
interaction too.

And what doesn't work, is only the first full backup - incrementals would be 
no problem once the full is done. Not the solution, right?

> > 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.

I'm not saying it should be a feature. I'm asking is there a way to do it, eg. 
by changing smth in database, rescanning the volume etc.

What could also help and what looks more like a feature, is ability to run a 
job from a failed job (using a failed full as basis for incremental), which is 
exactly what I want.

--
Silver

------------------------------------------------------------------------------
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

<Prev in Thread] Current Thread [Next in Thread>