Hello all

How do you get bacula to start at boot. Is it simply a case of moving relevant configuration files to the /etc/init.d dir?

Or did i miss a step when installing and configuring bacula?

I have bacula all up and working so dont want to do anything that may mess up the setup i.e. move files and then find bacula doesnt work no more!

Thanks for any help!

t.

bacula I think, is some sort of backup-manager.

How do you normally start it?
Do you start it as the user root, or as yourself?
Does it need to run all the time, or just when you want to make a backup?

keep configuration somewhere in /etc/ directory and /etc/init.d/ usually having startup scripts

Hi the startup scripts which i thought would be located in the /etc/init.d/ dir are not there for bacula. I only discovered this after rebooting the system only to find out that no backups were made for that day as the bacula server was down (it wasnt restarted when the server was rebooted.)...

I normally start it via webmin which has the bacula module included or if i do via the command line (rarely) i would change directory to the bacula installation and then issue a command like 'sudo ./bacula start'. Its storage, director and file daemons always run in the background...I would only restart the bacula server maybe to apply changes to the config files or if something went really wrong with the backups...so the bacula server is and should always be running.

Hope this has answered all your questions!

I've just placed the bacula script that starts the daemons (the bacula file in the /etc/bacula dir) into the /etc/init.d dir. I'm hoping that this works, but I cant really test without restarting the server which isnt really ideal at the moment. As the postgresql server (which is done at startup) needs to be up and running before the bacula server can start is there anyway that this can be done i.e. after postgresql servers are up and running then execute the bacula server start up script...hope im making sense...

Depending on your distro, you'll need to make symlinks in the appropriate rcX.d dirs, pointing at your startup script, or it won't be run.

Easiest may be to let /etc/rc.local start it up. The commands in rc.local are run (as root) after everything else has started up.

Make sure startupscript is set as executable, and writable only by root.

Then put /path/to/bacula/startscript into rc.local just before the final exit 0

That's it.