New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReaR + Bareos >16.2 new configuration path/filename structure #1077
Comments
@aussendorf Could you have a look at this issue and suggest updates, comments, etc...? |
workaround for #1077 (Bareos new conf directories)
@aussendorf We cannot fix it for ReaR 2.0 - it is too late now |
Hello @jsmeix and @gdha , sorry for my late reply. I've seen the workaround by @amtuannguyen, which looks like a good approach. As bareos-fd and bconsole don't require a "-c" parameter, I suggest to leave it away. Both binaries will
Unless someone is using another config-filename, in this case an additional option would be needed (but that case wasn't covered anyway). For the requirement checking I recommend to use -t, as it will check, if a configuration exists and can be loaded. |
@aussendorf Hi Maik - thank you for your insight into this matter (as SME). If you can improve the code do not hesitate and prepare a small pull request. |
Ok, I've also replaced greps in configfiles by calls to the program with -xc, which dumps the config. I've no testing environment at hand right now, so I will probably not be able to test it before next week. |
Since #1169 @aussendorf |
Hi, |
@ivveh You need the current ReaR upstream master code. How to test the currently newest ReaR GitHub master code Basically "git clone" it into a directory and then # git clone https://github.com/rear/rear.git # cd rear # vi etc/rear/local.conf # usr/sbin/rear -d -D mkbackup (note the relative paths "etc/rear/" and "usr/sbin/"). |
@jsmeix |
@ivveh Such explicit positive feedback helps us a lot I always think I should have a look at third-party backup tools |
@jsmeix |
Relax-and-Recover (rear) Issue Template
Please fill in the following items before submitting a new issue (quick response is not guaranteed with free support):
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
BACKUP=BAREOS
OUTPUT=USB
OUTPUT_URL="usb:///dev/disk/by-label/REAR-000"
Since Bareos changed its configuration paths:
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-1060008.1.2
Release Notes: http://doc.bareos.org/master/html/bareos-manual-main-reference.html#ReleaseNotes
tree /etc/bareos/
/etc/bareos/
└── bareos-fd.d
├── client
│ └── myself.conf
├── director
│ ├── bareos-dir.conf
│ └── bareos-mon.conf
└── messages
└── Standard.conf
the following error occurs:
rear -v mkrescue
Relax-and-Recover 1.19 / Git
Using log file: /var/log/rear/rear-sandbox201610.log
ERROR: Bareos configuration file (bareos-fd.conf) missing
Aborting due to an error, check /var/log/rear/rear-sandbox201610.log for details
[1] 9490 terminated rear -v mkrescue
manually fix Bareos settings in:
/usr/share/rear/prep/BAREOS/default # ls
40_prep_bareos.sh
45_check_BAREOS_client_configured.sh
50_check_BAREOS_bconsole_results.sh
55_check_bareos_restore_jobs.sh
56_check_bareos_filesets.sh
e.g. nano /usr/share/rear/prep/BAREOS/default/45_check_BAREOS_client_configured.sh
Tried with Bareos Version: 16.2.4
dpkg -l | grep bareos
ii bareos-common 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - common files
ii bareos-filedaemon 16.2.4-12.1 amd64 Backup Archiving Recovery Open Sourced - file daemon
The text was updated successfully, but these errors were encountered: