relative to bareos, I am in a learning curve, no lessons to give, but a lot to learn 
I am currently working to make a rpm, it seems to work well, however I noticed two things to make the backup on a remote nethserver 7
config set bareos-fd service status enabled TCPPort 9102 access green
for client, only the service bareos-fd is needed, it listens on port 9102, the other can be opened but is not needed.
However after the first signal-event runlevel-adjust the service will be down, to make it persistent:
[root@ns7loc10 ~]# mkdir /etc/e-smith/db/configuration/defaults/bareos-fd
[root@ns7loc10 ~]# echo 'service' > /etc/e-smith/db/configuration/defaults/bareos-fd/type
[root@ns7loc10 ~]# echo 'enabled' > /etc/e-smith/db/configuration/defaults/bareos-fd/status
you can test it
signal-event runlevel-adjust
systemctl status bareos-fd
the second things, maybe due to my development environment tricked…but I needed to put in /etc/hosts the hostname definition of the backup server in the client
in /etc/hosts of the client
192.168.56.12 ns7loc11.nethservertest.org ns7loc11
after this it seems to work.
I am looking now to make the authentication workable with PAM, it could be fun to have the same users between the web ui and nethserver, do you have some experiences with PAM and bareos to share.