On 04/06/10 02:36, Craig Ringer wrote:
> where they're all pretty repetitive except for the retention periods and
> volume names. I'm wondering if it'd be worth thinking about extending
> the director's pool config with a shorthand to allow easier
> configuration of full/diff/incr pool sets. Here, the Incremental{},
> Differential{} and Full{} sections inherit the defaults defined by their
> container, so you only have to define the overrides for different job
> levels.
>
> Pool {
> Name = "SystemPool"
> Storage = "File_System"
> Pool Type = Backup
> Recycle = yes
> AutoPrune = yes
> Volume Use Duration = 1 day
> Recycle Oldest Volume = yes
> AddLevelSuffix = yes # NEW DIRECTIVE
> LabelFormat = "System-"
> Incremental {
> Volume Retention = 1 week
> }
> Differential {
> Volume Retention = 2 weeks
> }
> Full {
> Volume Retention = 2 months
> }
> }
>
>
> Does this look like a reasonable way to simplify configuration of
> retention periods for jobs? It'd basically be a configuraton that
> logically expanded into three pools with mostly-common config.
Well, actually, no, it looks like a way of complicating pool definition,
not simplifying it. Because under this scheme, the pool syntax would
have to contain level-specific overrides for essentially every
adjustable parameter.
--
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.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
