Hi all, while at the spot, I remarked that my feature request from about maybe 2 years ago which are to be found in the kernstodo file
http://bacula.svn.sourceforge.net/viewvc/bacula/trunk/bacula/kernstodo?revision=8661&view=markup have not made it into the projects file. I however still think, these would be nice additions to bacula. I've copied the relevant text from the file to the bottom of the Mail. 2. I think Item 10 and Item 32 are more or less the same, not to be sound arrogant but I think Item 32 is more intutive, easier to implement and gives more flexibility (IMHO). Below is what I've submitted a long time ago, could we still get that into the projects file? Regards Carsten Line: 728 1. NextJob/NextJobs Directive within a Job Resource in the form of NextJobs = job1,job2. Why: I currently solved the problem with running multiple jobs each after each by setting the Max Wait Time for a job to 8 hours, and give the jobs different Priorities. However, there scenarios where 1 Job is directly depending on another job, so if the former job fails, the job after it needn't to be run while maybe other jobs should run despite of that Example: A Backup Job and a Verify job, if the backup job fails, there is no need to run the verify job, as the backup job already failed. However, one may like to backup the Catalog to disk despite of that the main backup job failed. Notes: I see that this is related to the Event Handlers which are on the ToDo list, also it is maybe a good idea to check for the return value and execute different actions based on the return value Added: 06th May 2009 Also you have then 3 Jobs marked as failed in bweb, which irritates users, instead of just showing that the backup job has failed and the others did not run because of that. 2nd, with this feature you can create really powerfull waterfall principles, elimating the need for concurrenct jobs runnig with the same priority somehow and solves even some scheduling problems with Max Wait Time etc. Line: 773 5. Setting Volume State within a Job Resource Why: Instead of using "Maximum Volume Jobs" in the Pool Resource, I would have the possibilty to define in a Job Resource that after this certain job is run, the Volume State should be set to "Volume State = Used", this give more flexibility -- "There are two major products that came out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence." --Jeremy S. Anderson ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
