Director resource type may be one of the following, presented here in the most logical order for defining them.
(Note: everything revolves around a Job and is tied to a Job in one way or another.)
To define the Director's name and its access password used for authenticating the Console program.
Only a single Director resource definition may appear in the Director's configuration file.
If you have either /dev/random or bc on your machine, Bacula will generate a random password during the configuration process, otherwise it will be left blank.
To define a backup/restore job and to tie together the Client, FileSet and Schedule resources to be used for each Job.
Normally, you will define Jobs of different names corresponding to each client (i.e. one Job per client, but a different one with a different name for each client).
Optional resource for providing defaults for Job resources.
To define when a Job is to be automatically run by Bacula's internal scheduler. You may have any number of Schedules, but each job will reference only one.
To define the set of files to be backed up for each Client.
You may have any number of FileSets but each Job will reference only one.
To define what Client is to be backed up. You will generally have multiple Client definitions. Each Job will reference only a single client.
To define on what physical device the Volumes should be mounted. You may have one or more Storage definitions.
To define the pool of Volumes that can be used for a particular Job.
Most people use a single default Pool. However, if you have a large number of clients or volumes, you may want to have multiple Pools. Pools allow you to restrict a Job (or a Client) to use only a particular set of Volumes.
To define in what database to keep the list of files and the Volume names where they are backed up.
Most people only use a single catalog. However, if you want to scale the Director to many clients, multiple catalogs can be helpful.
Multiple catalogs require a bit more management because in general you must know what catalog contains what data. Currently, all Pools are defined in each catalog. This restriction will be removed in a later release.
To define where error and information messages are to be sent or logged.
You may define multiple different message resources and hence direct particular classes of messages to different users or locations (files, …).
In each of these sections, the directives will be listed as “name = type”; the type signifies what sort of data is expected after the equals sign. What that value will *mean* is defined in the following paragraph.