Went to retest the writeset limit, and found I can't unless I want to clear another set of tapes, because bacula-9.0.8 is still overriding job parameters I enter manually with what the schedule says.
I went to run a manual full backup of this machine, which backs up about 528.000 files. The console said: run job="Babylon5 Backup" fileset="Gentoo Full Set" level="Full" client="babylon5" pool="Full-Disk" storage="asgard-file" priority="10" when="2018-08-08 11:45:19" yes Job queued. JobId=19966 Which is what I entered. But when I look at running jobs, Bacula has changed the Storage to babylon5-sd and the Pool to Full-Tape. I am going to opine once again that Bacula should NEVER silently override job parameters entered by the administrator via the console. It's the administrator's *job* to know what resources are valid for a job, and most of the time the administrator is going to be right. If Bacula thinks I have entered wrong or invalid parameters, AT MOST it should notify me that it thinks they're wrong and ask if I want them changed. It should NEVER change them without asking me first or telling me that it changed them. I can't run a test backup to an ephemeral file that I can just throw away when I'm done, without first either creating a new Job or changing the controlling Schedule, not because I don't have the resources or because the destination is invalid, but because Bacula thinks it knows better than I do and I didn't actually intend to do that. This behavior really needs to be fixed. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
