On 06/28/11 09:10, Graham Keeling wrote:
> On Tue, Jun 28, 2011 at 08:40:47AM -0400, John Drescher wrote:
>> I think the idea is to terminate early without error. So that the next
>> incremental ... can pickup where the full left off.
>
> Surely the only difference between an interrupted incremental and a completed
> incremental is that the most recently transmitted file in the former might
> be broken.
>
> So, I don't see why bacula can't just treat an interrupted incremental as a
> finished incremental, except for the single file that was being transmitted
> at the point of interruption.
I had the same thought. It might perhaps require a new job termination
status, "Incomplete". This could also be useful for backing up, say,
laptops, where the user might take their machine out of wireless range
(or shut it down to take it home) in the middle of a backup.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
