In any case the file is there and configured (by default?), so I guess the
error is due to the single letter -x switches?
#
# Bareos User Agent (or Console) Configuration File
#
Director {
Name = bareos-dir
address = localhost
Password = "secret"
Description = "Bareos Console credentials
According to the error it seems the director is required to be installed on
the client side when using rear, right?
The client is backed up with no issues without the director being
installed, only rear does not work.
On Thursday, February 1, 2024 at 12:19:29 PM UTC+2 Bruno Friedmann
(bruno-at-
a director ressource is mandatory to make bareos-fd able to know who is
connecting.
rear is also using bconsole, which also need a director ressource to
connect to.
but of course that doesn't mean bareos-director component has to be
installed, this is 2 separated things.
Le jeudi 1 février 202
No, I was not sure director is needed on the client end, is it needed?
On Wednesday, January 31, 2024 at 11:42:55 AM UTC+2 Jürgen Echter wrote:
> Hi,
>
> you have to configure ther director in bconsole.conf.
>
> Like this:
>
> #
> # Bareos User Agent (or Console) Configuration File
> #
> Director
Not sure it will be enough due to the following trace reported
2024-01-30 12:20:54.433433584 Including
prep/BAREOS/default/500_check_BAREOS_bconsole_results.sh
The -xc and -xs options have changed.
Use --xc and --xs as given in the help.
Run with --help for more information.
2024-01-30 12:20:
Hi,
you have to configure ther director in bconsole.conf.
Like this:
#
# Bareos User Agent (or Console) Configuration File
#
Director {
Name = bareos-dir
address = xx.xx.xx.xx
Password = "secret"
Description = "Bareos Console credentials for local Director"
}
Greetings
Juergen
Hi,
Trying to configure client for DR with rear following this guide
https://docs.bareos.org/Appendix/DisasterRecoveryUsingBareos.html.
Client is being backed up with no issues.
After completed configuration and running rear -v mkrescue I get this
error: Director not configured in bconsole s
