
Bacula 1.30 User's Guide
|
Chapter 5.2
|
|
 |
Director Configuration
|
Index
|
Storage Daemon Configuration
|
|
|
Client/File daemon Configuration
General
The Client (or File Daemon) Configuration is one of the
simpler ones to specify. Generally, other than changing
the Client name so that error messages are easily identified,
you will not need to modify the default Client configuration
file.
For a general discussion of configuration file and resources
including the data types recognized by Bacula, please
see the Configuration chapter of this
manual.
The following Client Resource definitions must be defined:
- Client -- to define what Clients are
to be backed up.
- Director -- to
define the Director's name and its access password.
- Messages -- to define where error
and information messages are to be sent.
The Client Resource (or FileDaemon) resource defines the name
of the Client (as used by the Director) as well as the port on
which the Client listens for Director connections.
- Client (or FileDaemon)
- Start of the Client records.
There must be one and only one Client resource in the
configuration file, since it defines the properties of the
current client program.
- Name = <name>
- The client name that must be used
by the Director when connecting. Generally, it is a good idea
to use a name related to the machine so that error messages
can be easily identified if you have multiple Clients.
This record is required.
- Working Directory = <Directory>
- This directive
is mandatory and specifies a directory in which the File daemon
may put its status files. This directory should be used only
by Bacula, but may be shared by other Bacula daemons. This
record is required
- Pid Directory = <Directory>
- This directive
is mandatory and specifies a directory in which the Director
may put its process Id file files. The process Id file is used to
shutdown Bacula and to prevent multiple copies of
Bacula from running simultaneously.
This record is required. Standard shell expansion of the Directory
is done when the configuration file is read so that values such
as $HOME will be properly expanded.
Typically on Linux systems, you will set this to:
/var/run. If you are not installing Bacula in the
system directories, you can use the Working Directory as
defined above.
- SubSys Directory = <Directory>
- This directive
is mandatory and specifies a directory in which the Director
may put its subsystem lock files. This
record is required. Standard shell expansion of the Directory
is done when the configuration file is read so that values such
as $HOME will be properly expanded.
Typically on Linux systems, you will set this to:
/var/run/subsys. If you are not installing Bacula in the
system directories, you can use the Working Directory as
defined above. Take care that you do not set this to the
same directory that contains your binary files or they will be
deleted.
- Maximum Concurrent Jobs = <number>
- where <number>
is the maximum number of Jobs that should run concurrently. The
default is set to 2, but you may set it to a larger number. Each
contact from the Director (e.g. status request, job start request) is
considered as a Job, so if you want to be able to do a status
request in the console at the same time as a Job is running, you
will need to set this value greater than 1.
- FDPort = <port-number>
- This specifies the port number
on which the Client listens for Director connections. It must agree
with the FDPort specified in the Client resource of the Director's
configuration file. The default is 9102.
- FDAddress = <IP-Address>
- This record is optional,
and if it is specified, it will cause the File daemon server (for
Director connections) to bind to the specified IP-Address,
which is either a domain name or an IP address specified as a
dotted quadruple. If this record is not specified, the File daemon
will bind to any available address (the default).
The following is an example of a valid Client resource definition:
Client { # this is me
Name = rufus-fd
WorkingDirectory = $HOME/bacula/bin/working
Pid Directory = $HOME/bacula/bin/working
SubSys Directory = $HOME/bacula/bin/working
}
The Director resource defines the name and password of the
Directors that are permitted to contact this Client.
- Director
- Start of the Director records. There may be any
number of Director resources in the Client configuration file. Each
one specifies a Director that is allowed to connect to this
Client.
- Name = <name>
- The name of the Director
that may contact this Client. This name must be the
same as the name specified on the Director resource
in the Director's configuration file. This record is required.
- Password = <password>
- Specifies the password that must be
supplied for a Director to be authorized. This password
must be the same as the password specified in the
Client resource in the Director's configuration file.
This record is required.
Thus multiple Directors may be authorized to use this Client's services.
Each Director will have a different name, and normally a different password
as well.
The following is an example of a valid Director resource definition:
#
# List Directors who are permitted to contact the File daemon
#
Director {
Name = HeadMan
Password = very_good \# password HeadMan must supply
}
Director {
Name = Worker
Password = not_as_good
}
Please see the Messages Resource
Chapter of this manual for the details of the Messages Resource.
There must be at least one Message resource in the Client
configuration file.
An example File Daemon configuration file might be the following:
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 1.15 (5 March 2002) -- redhat 7.1
#
# There is not much to change here except perhaps to
# set the Director's name and File daemon's name
# to something more appropriate for your site.
#
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = rufus-dir
Password = "/LqPRkX++saVyQE7w7mmiFg/qxYc1kufww6FEyY/47jU"
}
#
# "Global" File daemon configuration specifications
#
FileDaemon { \# this is me
Name = rufus-fd
WorkingDirectory = $HOME/bacula/bin/working
Pid Directory = $HOME/bacula/bin/working
SubSys Directory = $HOME/bacula/bin/working
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = rufus-dir = all, !skipped
}
Director Configuration
|
Index
|
Storage Daemon Configuration
|
|
 |
|
|