Bacula/woozle

2009-02-24 11:09
I'm damned if I can figure out how to get this thing to run. "bat" can't connect to localhost because "bacula-director" won't run; bacula-director won't run because /etc/bacula/bacula-dir.conf hasn't been set up, which requires jobs to be created. I can't create jobs because I can't get any of the console tools to run (bat, bconsole, etc.) because bacula-director isn't running. Are you supposed to manually enter job information, or what? Where is this explained?

Sophisticated tools with lame interfaces tick me off. There should be a program you run which lets you set things up through a GUI, or at least an interactive process where you don't have to understand the arcane requirements of some application's conf file. (Also the fact that it apparently has its own open-but-unique storage format seems kind of stupid; what is the benefit?) --Woozle 11:09, 24 February 2009 (EST)

2010-03-19
Some discoveries:
 * Use Webmin to configure it. Much easier.
 * The "director" is the thing which runs a backup. Clients (aka "file daemons") need to add accounts for each director they authorize to contact them; this is referred to as adding a director. So if you have machine A which is your server and B which has files you want to back up --
 * On B, under "File Daemon Configuration", get B's "File daemon name" (e.g. "B-fd")
 * On A, under "Backup Clients", add a new client called "B-fd" (make up the password)
 * On A, under "Director Configuration", get A's "Director name" (e.g. "A-dir")
 * On B, under "File Daemon Directors", add a new director called "A-dir", using the same password from step 2
 * You can verify that this worked from A by checking "Client Status" (under the "Backup and Restore Actions" section). The status should come back in less than a second. If it takes longer than that, it is probably having trouble connecting, and will show an error message in 10-20 seconds; just wait a bit to be sure.