From: Phil S. <al...@me...> - 2011-05-31 13:08:45
|
Yes, this bit me again this morning. The backup job for my main server specifies disk for Incremental and Differential pools, and LTO2 tape for Full pool. Since my LTO2 drive seems to be having issues right now, I went to manually run a Full backup to the full disk pool instead. I couldn't figure out why the job wasn't starting, until I looked at the Director status and saw that it was waiting on the storage device that runs my tape drive ... which was the point at which I remembered that the FullPool directive and its friends override the pool manually specified in the console. What's worse, they do so silently. I have to consider this to be a [potentially serious] bug. Parameters specified in the console should ALWAYS override, but in particular, a console override that *SILENTLY* doesn't actually override what it says it's overriding could potentially result in loss of data or job failure. (In fact, in this case it *did* result in job failure.) Going to check on Mantis and see if I already filed a bug report against this, and see if I can somehow make time to come up with a patch. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 al...@ca... al...@me... ph...@co... Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater It's not the years, it's the mileage. |