Hello,
From time to time, I've heard some complaints about the way Bacula selects
pools, but it has never been specific enough for me to do something. Now, I
have an example where I have defined an Incremental Pool, and in using the
"run" command, even though the job is an Incremental job, the pool show is
the Full Pool.
In looking at the code, I see the following:
1. When (if) a job is scheduled, the Run pool overrides are applied to the
pool.
2. If you manually run a job, it starts here.
3. When the backup is initialized, the Job pool specifications are applied,
if any.
4. If the backup is Diff or Inc, and no Full backup is found in the catalog,
the job is upgraded to Full.
Now, I haven't looked at this in detail, but it seems to me that at least in
1.37, the Job pool specifications are not working as I intended, since step 4
should logically be done before step 3.
Also, I haven't checked the documentation, but it should clearly indicate that
Job Pool specifications (other than the Pool = ) override any run overrides.
Comments would be appreciated as I would like to fix this problem.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
