Phil Stracchino schrieb: > > ... > > I am not even sure how one might go about > > resolving the problem: > > > > 1. Make manually overriding the Pool when starting a Job take precedence > > over > > all other Pool specifications? I don't particularly like that idea. > > It seems to be to be the obvious approach. If I'm starting a job > manually and choosing to manually override the Pool, then that override > should be honored - period - because if I, as a Bacula administrator, > choose as a conscious and separate manual operation to override the Pool > for a job I'm about to manually start, the odds are pretty high that I > have a good reason for doing so. If a manual override does NOT override > other Pool specifications, then what's the point of having a manual > override for the Pool? It's rather inherent in the concept of having a > manual override. > ...
+1 from me I was just bitten by that. One of our 3 LTO-4 drives seems to have problems. To eliminate other sources of error I started a job manually in bconsole and specified a different drive and pool for this job. But due to the pool definition for this job, the pool and the storage device I specified in bconsole wasn't honored. This is highly confusing and error prone. Ralf ------------------------------------------------------------------------------ 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
