[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-bugs
Subject:    [Bacula-bugs] [bacula 0001044]: Scheduled jobs gets there "level"
From:       bacula-bugs () lists ! sourceforge ! net
Date:       2008-01-25 9:18:31
Message-ID: 3885b9af8a148ae8ce6e1a4c5eb5067c () bugs ! bacula ! org
[Download RAW message or body]


The following issue has been CLOSED 
====================================================================== 
http://bugs.bacula.org/view.php?id=1044 
====================================================================== 
Reported By:                jesperkrogh
Assigned To:                
====================================================================== 
Project:                    bacula
Issue ID:                   1044
Category:                   Director
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Resolution:                 Added to TO DO List
Fixed in Version:           
====================================================================== 
Date Submitted:             01-25-2008 09:09 UTC
Last Modified:              01-25-2008 09:18 UTC
====================================================================== 
Summary:                    Scheduled jobs gets there "level" assigned at
Scheduling time not at "Run time.
Description: 
I have a 2.4TB disk that takes around 48 hours to process "Full", but when
24 hours has elapsed another "Incremental" job is put into the Scheduling
list, automatically upgraded to Full because there has been no prior
Full-jobs successfully run. The systems might be clever enough to make this
check before actually running the job instead of before scheduling the job.



====================================================================== 

---------------------------------------------------------------------- 
 kern - 01-25-08 09:18  
---------------------------------------------------------------------- 
Sorry, but this the current implementation and thus is not really a bug but
a Feature Request. We have a development project in the next version to
correct this.

You shouldn't have any single job that runs more than say 12 hours maximum
otherwise you will surely have nothing but problems either in the backup or
in the restore phase. The bacula-users list can probably help you in this
respect. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-25-08 09:09  jesperkrogh    New Issue                                    
01-25-08 09:18  kern           Note Added: 0003090                          
01-25-08 09:18  kern           Status                   new => closed       
01-25-08 09:18  kern           Resolution               open => Added to TO DO
List
======================================================================


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-bugs mailing list
Bacula-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-bugs
[prev in list] [next in list] [prev in thread] [next in thread]