Menu
▾
▴
[Bacula-bugs] [bacula 0000548]: Job cloning ("Run = ....") does not handle the specified Pool argument
|
From: <bac...@li...> - 2006-02-21 21:01:09
|
A BUGNOTE has been added to this bug. ====================================================================== http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000548 ====================================================================== Reported By: malguy-solsoft Assigned To: ====================================================================== Project: bacula Bug ID: 548 Category: Director Reproducibility: always Severity: feature Priority: normal Status: new ====================================================================== Date Submitted: 02-21-2006 04:37 PST Last Modified: 02-21-2006 13:01 PST ====================================================================== Summary: Job cloning ("Run = ....") does not handle the specified Pool argument Description: I want to write the same data to two different places (storage), using two different pools. So I use the ability to clone a job with the Run attribute inside a Job resource. Despite the fact I indicate an alternative pool to use, the cloned job uses the same pool as uses the original job. From the documentation, I read: "The part after the equal sign [...] can contain any string or set of options (overrides) that you can specify when entering the Run command from the console" About the Run command from the console, the documentation gives the following options: "run job=<job-name> client=<client-name> fileset=<FileSet-name> level=<level-keyword> storage=<storage-name> where=<directory-prefix> when=<universal-time-specification> yes" where is nothing about a pool option. However, using bconsole, I can do the following: *run job=job-test storage=dlt-storage pool=cart-month Run Backup job JobName: job-test FileSet: file-test Level: Full Client: atlas-fd Storage: dlt-storage Pool: cart-month When: 2006-02-21 13:33:26 Priority: 10 OK to run? (yes/mod/no): . So I wonder: is the pool options only available from console ? Is the documentation incomplete ? Is the Run attribute from a Job resource missing something ? Anyway, I really wish to have the possibility to specify an alternate pool cloning a job. ====================================================================== ---------------------------------------------------------------------- malguy-solsoft - 02-21-2006 09:45 PST ---------------------------------------------------------------------- I think I just understood the point: The Pool=cart-month from Run = "..." is not ignored, but overrided by the Full Backup Pool attribute of the Job. I guess it's obvisouly, but I missed it before. If that's it, is it possible to provide an alternate full/differential/incremental backup pool ? ---------------------------------------------------------------------- ArnoL - 02-21-2006 13:01 PST ---------------------------------------------------------------------- I might have overlooked this in my mail, but the mailing lists might be a better place to discuss this sort of stuff- You are right, the job definition's Full Backup Pool setting wins when you specify other options in the run directive. There are several solutions: Don't use Full Backup Pool=, set the pool in the schedule instead (like you do with the run directive). This one is probably the easiest solution. You might also consider using the python interface, though I'm not sure it actually allows what you need. Finally, observe the development concerning job migration - copying *might* follow soon. Bug History Date Modified Username Field Change ====================================================================== 02-21-06 04:37 malguy-solsoft New Bug 02-21-06 04:51 malguy-solsoft Bug Monitored: malguy-solsoft 02-21-06 09:45 malguy-solsoft Bugnote Added: 0001475 02-21-06 13:01 ArnoL Bugnote Added: 0001476 ====================================================================== |