On lundi, 5 septembre 2016 00.30:20 h CEST Daniel wrote: > Hi, > > i use bareos to backup some webservers, but also some computers. The pcs > aren't 24/7 online, so sometimes bareos tries to backup them und throws an > error. (Warning: bsock_tcp.c:128 Could not connect to Client: titan-fd on > name:9102. ERR=Keine Route zum Zielrechner Retrying ... > Fatal error: bsock_tcp.c:134 Unable to connect to Client: titan-fd on > name:9102. ERR=Unterbrechung wÀhrend des Betriebssystemaufrufs). I want to > change the behaviour, so that I won't get an error. Instead of that bareos > should check, if the client is available. If he is, the backup can be done > and if not, bareos should try it x hours later again, without throwing an > error. Only if during y days no backup could be done, bareos should throw > an error. Is there any posssibility to do that? > Which solution choose other users with similar problems?
I use Runscript with before and have script that ping the target host. if not present I'm using the retry on error instruction to retry during 4 times in the next 4 hours. Have a look at http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirJobRun Have fun -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.7.2-1-default x86_64 GNU/Linux, nvidia: 370.23 Qt: 5.6.1, KDE Frameworks: 5.25.0, Plasma: 5.7.4, kmail2 5.3.0 (QtWebEngine) -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
