Monitor Configuration
The Monitor configuration file is a stripped down version of the Director configuration file, mixed with a Console configuration file. It simply contains the information necessary to contact Directors, Clients, and Storage daemons you want to monitor.
For a general discussion of configuration file and resources including the data types recognized by Bareos, please see the Configuration chapter of this manual.
The following Monitor Resource definition must be defined:
Monitor – to define the Monitor’s name used to connect to all the daemons and the password used to connect to the Directors. Note, you must not define more than one Monitor resource in the Monitor configuration file.
At least one Client, Storage or Director resource, to define the daemons to monitor.
Monitor Resource
The Monitor resource defines the attributes of the Monitor running on the network. The parameters you define here must be configured as a Director resource in Clients and Storages configuration files, and as a Console resource in Directors configuration files.
configuration directive name |
type of data |
default value |
remark |
---|---|---|---|
= |
|||
= |
10 |
||
= |
no |
||
= |
10 |
||
= |
required |
||
required |
|||
= |
60 |
||
= |
10 |
||
= |
no |
||
= |
yes |
||
= |
|||
= |
yes |
||
= |
no |
- Enable kTLS
- Type:
- Default value:
no
If set to “yes”, Bareos will allow the SSL implementation to use Kernel TLS.
- Name
- Required:
True
- Type:
Specifies the Director name used to connect to Client and Storage, and the Console name used to connect to Director. This record is required.
- Password
- Required:
True
- Type:
Where the password is needed for Directors to accept the Console connection. This password must be identical to the Password specified in the Console resource of the Director’s configuration file. This record is required if you wish to monitor Directors.
- Refresh Interval
- Type:
- Default value:
60
Specifies the time to wait between status requests to each daemon. It can’t be set to less than 1 second or more than 10 minutes.
- TLS Allowed CN
- Type:
“Common Name”s (CNs) of the allowed peer certificates.
- TLS Cipher Suites
- Type:
Colon separated list of valid TLSv1.3 Ciphers; see openssl ciphers -s -tls1_3. Leftmost element has the highest priority. Currently only SHA256 ciphers are supported.
- TLS DH File
- Type:
Path to PEM encoded Diffie-Hellman parameter file. If this directive is specified, DH key exchange will be used for the ephemeral keying, allowing for forward secrecy of communications.
- TLS Key
- Type:
Path of a PEM encoded private key. It must correspond to the specified “TLS Certificate”.
- TLS Require
- Type:
- Default value:
yes
If set to “no”, Bareos can fall back to use unencrypted connections.
Director Resource
The Director resource defines the attributes of the Directors that are monitored by this Monitor.
As you are not permitted to define a Password in this resource, to avoid obtaining full Director privileges, you must create a Console resource in the Director’s configuration file, using the Console Name and Password defined in the Monitor resource. To avoid security problems, you should configure this Console resource to allow access to no other daemons, and permit the use of only two commands: status and .status (see below for an example).
You may have multiple Director resource specifications in a single Monitor configuration file.
configuration directive name |
type of data |
default value |
remark |
---|---|---|---|
= |
required |
||
= |
|||
= |
9101 |
||
= |
no |
||
= |
required |
||
= |
no |
||
= |
yes |
||
= |
|||
= |
yes |
||
= |
no |
- Address
- Required:
True
- Type:
Where the address is a host name, a fully qualified domain name, or a network address used to connect to the Director. This record is required.
- Dir Port
- Type:
- Default value:
9101
Specifies the port to use to connect to the Director. This port must be identical to the DIRport specified in the Director resource of the Director Configuration file.
- Enable kTLS
- Type:
- Default value:
no
If set to “yes”, Bareos will allow the SSL implementation to use Kernel TLS.
- Name
- Required:
True
- Type:
The Director name used to identify the Director in the list of monitored daemons. It is not required to be the same as the one defined in the Director’s configuration file. This record is required.
- TLS Allowed CN
- Type:
“Common Name”s (CNs) of the allowed peer certificates.
- TLS Cipher Suites
- Type:
Colon separated list of valid TLSv1.3 Ciphers; see openssl ciphers -s -tls1_3. Leftmost element has the highest priority. Currently only SHA256 ciphers are supported.
- TLS DH File
- Type:
Path to PEM encoded Diffie-Hellman parameter file. If this directive is specified, DH key exchange will be used for the ephemeral keying, allowing for forward secrecy of communications.
- TLS Enable
- Type:
- Default value:
yes
Enable TLS support.
Bareos can be configured to encrypt all its network traffic. See chapter TLS Configuration Directives to see how the Bareos Director (and the other components) have to be configured to use TLS.
- TLS Key
- Type:
Path of a PEM encoded private key. It must correspond to the specified “TLS Certificate”.
- TLS Require
- Type:
- Default value:
yes
If set to “no”, Bareos can fall back to use unencrypted connections.
Client Resource
The Client resource defines the attributes of the Clients that are monitored by this Monitor.
You must create a Director resource in the Client’s configuration file, using the Director Name defined in the Monitor resource. To avoid security problems, you should set the Monitor directive to Yes in this Director resource.
You may have multiple Director resource specifications in a single Monitor configuration file.
configuration directive name |
type of data |
default value |
remark |
---|---|---|---|
= |
required |
||
= |
|||
= |
no |
||
= |
9102 |
||
= |
required |
||
required |
|||
= |
no |
||
= |
yes |
||
= |
|||
= |
yes |
||
= |
no |
- Address
- Required:
True
- Type:
Where the address is a host name, a fully qualified domain name, or a network address in dotted quad notation for a Bareos File daemon. This record is required.
- Enable kTLS
- Type:
- Default value:
no
If set to “yes”, Bareos will allow the SSL implementation to use Kernel TLS.
- FD Port
- Type:
- Default value:
9102
Where the port is a port number at which the Bareos File daemon can be contacted.
- Name
- Required:
True
- Type:
The Client name used to identify the Director in the list of monitored daemons. It is not required to be the same as the one defined in the Client’s configuration file. This record is required.
- Password
- Required:
True
- Type:
This is the password to be used when establishing a connection with the File services, so the Client configuration file on the machine to be backed up must have the same password defined for this Director. This record is required.
- TLS Allowed CN
- Type:
“Common Name”s (CNs) of the allowed peer certificates.
- TLS Cipher Suites
- Type:
Colon separated list of valid TLSv1.3 Ciphers; see openssl ciphers -s -tls1_3. Leftmost element has the highest priority. Currently only SHA256 ciphers are supported.
- TLS DH File
- Type:
Path to PEM encoded Diffie-Hellman parameter file. If this directive is specified, DH key exchange will be used for the ephemeral keying, allowing for forward secrecy of communications.
- TLS Key
- Type:
Path of a PEM encoded private key. It must correspond to the specified “TLS Certificate”.
- TLS Require
- Type:
- Default value:
yes
If set to “no”, Bareos can fall back to use unencrypted connections.
Storage Resource
The Storage resource defines the attributes of the Storages that are monitored by this Monitor.
You must create a Director resource in the Storage’s configuration file, using the Director Name defined in the Monitor resource. To avoid security problems, you should set the Monitor directive to Yes in this Director resource.
You may have multiple Director resource specifications in a single Monitor configuration file.
configuration directive name |
type of data |
default value |
remark |
---|---|---|---|
= |
required |
||
= |
|||
= |
no |
||
= |
required |
||
required |
|||
= |
|||
= |
9103 |
||
= |
no |
||
= |
yes |
||
= |
|||
= |
yes |
||
= |
no |
- Address
- Required:
True
- Type:
Where the address is a host name, a fully qualified domain name, or a network address in dotted quad notation for a Bareos Storage daemon. This record is required.
- Enable kTLS
- Type:
- Default value:
no
If set to “yes”, Bareos will allow the SSL implementation to use Kernel TLS.
- Name
- Required:
True
- Type:
The Storage name used to identify the Director in the list of monitored daemons. It is not required to be the same as the one defined in the Storage’s configuration file. This record is required.
- Password
- Required:
True
- Type:
This is the password to be used when establishing a connection with the Storage services. This same password also must appear in the Director resource of the Storage daemon’s configuration file. This record is required.
- SD Password
- Type:
- SD Port
- Type:
- Default value:
9103
Where port is the port to use to contact the storage daemon for information and to start jobs. This same port number must appear in the Storage resource of the Storage daemon’s configuration file.
- TLS Allowed CN
- Type:
“Common Name”s (CNs) of the allowed peer certificates.
- TLS Cipher Suites
- Type:
Colon separated list of valid TLSv1.3 Ciphers; see openssl ciphers -s -tls1_3. Leftmost element has the highest priority. Currently only SHA256 ciphers are supported.
- TLS DH File
- Type:
Path to PEM encoded Diffie-Hellman parameter file. If this directive is specified, DH key exchange will be used for the ephemeral keying, allowing for forward secrecy of communications.
- TLS Key
- Type:
Path of a PEM encoded private key. It must correspond to the specified “TLS Certificate”.
- TLS Require
- Type:
- Default value:
yes
If set to “no”, Bareos can fall back to use unencrypted connections.
Traymonitor
Traymonitor Security
There is no security problem in relaxing the permissions on Bareos Traymonitor configuration files as long as Bareos File Daemon, Bareos Storage Daemon and Bareos Director are configured properly, so the passwords contained in this file only gives access to the status of the daemons. It could be a security problem if you consider the status information as potentially dangerous (most people consider this as not being dangerous).
Concerning Director’s configuration: In the Bareos Traymonitor configuration files the password in the Monitor resource must point to a restricted console in Bareos Director configuration. So, if you use this password with :command:` bconsole`, you’ll only have access to the status of the director (commands status and .status). It could be a security problem if there is a bug in the ACL code of the director.
Concerning File and Storage Daemons’ configuration: In the Bareos Traymonitor configuration files the Name in the Monitor resource must point to a Director resource in the Bareos File Daemon respectively Bareos Storage Daemon configuration, with the Monitor directive set to Yes.
Example Traymonitor configuration
An example Traymonitor configuration file might be the following: