#511 Issue closed
: Using Bareos+rear¶
Labels: support / question
, fixed / solved / done
pgporada opened issue at 2014-11-24 22:03:¶
I'm not sure if this is the correct place to write this, but I am having difficulty in configuring the bconsole.conf portion for use with rear.
Do I configure my clients /etc/bareos/bconsole.conf with the same Director and password that the Bareos server uses? If so, I am getting the following message
24-Nov 17:02 planetx-dir JobId 0: Fatal error: bsock.c:131 Unable to connect to Client: hale-bopp-fd on 192.168.1.10:9102. ERR=Connection refused
How do others configure this?
gdha commented at 2014-11-25 12:06:¶
Perhaps have a peek at http://www.bareos.org/en/HOWTO/articles/relax-and-recover-with-bareos.html
pgporada commented at 2014-11-25 20:52:¶
I was able to finally connect. I'll create some documentation on the process as it was unclear to me.
Something else I noticed was that during a Bareos restore, the BAREOS_CLIENT variable in
/usr/share/rear/restore/BAREOS/default/40_restore_backup.sh
looks for the entire hostname string in /etc/bareos/bareos-fd.conf. Shouldn't hostname -s typically be used instead of the FQDN?
Here is an example of what I mean.
[root@hale-bopp ~]# BAREOS_CLIENT=$(grep $(hostname) /etc/bareos/bareos-fd.conf | awk '/-fd/ {print $3}' )
[root@hale-bopp ~]# echo $BAREOS_CLIENT
[root@hale-bopp ~]# BAREOS_CLIENT=$(grep $(hostname -s) /etc/bareos/bareos-fd.conf | awk '/-fd/ {print $3}' )
[root@hale-bopp ~]# echo $BAREOS_CLIENT
hale-bopp-fd
Thank you for the response thus far.
gdha commented at 2014-11-26 13:49:¶
@pgporada I think that @aussendorf or @joergsteffens are better placed to give an answer on your question.
sebastianlederer commented at 2014-11-26 16:39:¶
Something else I noticed was that during a Bareos restore, the BAREOS_CLIENT variable in
/usr/share/rear/restore/BAREOS/default/40_restore_backup.sh
looks for the entire hostname string in /etc/bareos/bareos-fd.conf. Shouldn't hostname -s typically be used instead of the FQDN?
That is actually a bug which I will fix within the next few days. Also, I will add a configuration option to specify the client name directly.
gdha commented at 2014-12-05 16:49:¶
@sebastianlederer Any luck with an update to rear yet?
sebastianlederer commented at 2014-12-15 18:41:¶
Sorry for the late reply, it has been quite a busy week.
The (trivial) fix is in my rear fork, but I still had no chance to test it.
Hopefully I will get to it till the end of this week.
Best regards,
Sebastian Lederer
Am 05.12.2014 um 17:49 schrieb gdha:
@sebastianlederer https://github.com/sebastianlederer Any luck with an
update to rear yet?—
Reply to this email directly or view it on GitHub
https://github.com/rear/rear/issues/511#issuecomment-65817533.
gdha commented at 2015-01-23 07:35:¶
@sebastianlederer Kind reminder for making a pull request with your fix - thanks.
sebastianlederer commented at 2015-01-29 11:01:¶
Finally got around testing the fix, found a new bug and fixed that too. Tests are ok now.
gdha commented at 2015-02-03 09:25:¶
@sebastianlederer thank you for the fix.
[Export of Github issue for rear/rear.]