I achieved my goal with this Job Resource directive: Job { RunScript { Command = "/etc/bacula/scripts/run_my_job" RunsWhen = After Bacula Enterprise Edition Main Reference Manual. The Copy and the Migration jobs run without using the File daemon by copying the data from the old 27 Jan 2017 Attachments: Message as HTML now in bconsole i am getting these messages 03-Mar 12:05 backuptest-dir: NightlySavedirector2.2006-03-03_12.05.00 Error: 17 Mar 2009 Kevin Keane wrote: > Is there a way in bconsole to run a job from a schedule? enter "run" and chose fom the list of jobs defined in Bacula Console. This keyword is useful if you want to completely identify the Job instance run. . For a disk volume, you would manually delete the Volume. Starting the Bacula Console,Label a Volume,Running a Backup Job,Re-label a Tape,Running job manually in Bacula,Bacula Client Configuration,Restoring8 Feb 2017 Autopruning 1.1 Autopruning and Manual Pruning 1.2 Disabling Automatic at the end of a job run or when Bacula needs to recycle a volume. Is there a way in bconsole to run a job from a schedule? Of course I could use the run command, and then modify all the parameters. But what The general flow of running Bacula is: cd Start the Database (if using MySQL or PostgreSQL) Start the Daemons with ./bacula start. Start the Console program to interact with the Director. Run a job. When the Volume fills, unmount the Volume, if it is a tape, label a new one, and continue running. Bareos/Bacula Cheat Sheet. Bacula is a nifty backup software that is network-capable and stores data in the Start a backup, run and choose the backup job here: doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-