Hi Daniel, some of your questions have be discussed before. Please see https://groups.google.com/forum/#!topic/bareos-users/42J_PuE6J34 and https://groups.google.com/forum/#!topic/bareos-users/t4Ko2RIRjEc.
The issue you report is properly related to the network heartbeat. Please refer to https://groups.google.com/forum/#!topic/bareos-users/anj9TLyrYQA regards, Jörg On 26.03.2018 at 15:48 wrote Daniel: > Hello, > I have been using bareos for backups in the company for some time. Currently, > the backups are triggered at night. Since some colleagues turn off their > computers at night, I use the following settings: > MaxFullInterval = 1 months > MaxDiffInterval = 1 weeks > Reschedule On Error = yes > Reschedule interval = 2 hours > Reschedule Times = 8 > This will back up the computers until noon, if they are then switched on. > Now it can also be that colleagues are not in the office for a few days. I > then receive an e-mail every day that the backup has not been executed. I > would like to avoid that. > > The solution mentioned in the documentation is Client Initiated Connection. I > have now integrated them into a test environment. > I have added the following to > /etc/bareos/bareos-fd.d/director/bareos-dir.conf on the client: > Address = 192.168.1.233 #address of the backup server > Connection From Client to Director = yes > Connection From Director to Client = no > > I also added the following to the configuration of my client on the backup > server: > Heartbeat interval = 60 > Connection From Client To Director = yes > Connection From Director To Client = no > Passive = yes > Enabled = yes > > If I now run "status dir" on the backup server, I get: > Client initiated connections (waiting for jobs): > Connect time Protocol Authenticated Name > =================================================== > 26-Mar018 15:11 54 1 daniel VirtualBox-fd > > If I now start a job manually via bconsole, I first get "Using Client > Initiated Connection (daniel-VirtualBox-fd)" displayed, but later an error. > "Mar 26 14:46 bareos-sd JobId 5319: Warning: bsock_tcp.c:128 Could not > connect to File Daemon on 10.0.2.15:9102 ERR=The connection wait has expired > Retrying ... > 26-Mar 15:12 bareos-sd JobId 5319: Fatal error: bsock_tcp.c:134 Unable to > connect to File Daemon on 10.0.2.15:9102 ERR=interruption during operating > system call > 26-Mar 15:12 bareos-sd JobId 5319: Fatal error: Failed to connect to File > daemon: 10.0.2.15:9102 > 26-Mar 15:12 bareos-dir JobId 5319: Fatal error: Socket error on Passive > client command: ERR=No data available > 26-Mar 15:12 bareos-dir JobId 5319: Fatal error: Network error with FD during > Backup: ERR=No data available" > > What could be the reason for this? > And how does it work that a backup is created as soon as a client connects > and the last backup is older than one day? I know I can enforce full and > differential backup using MaxFullInterval = 1 months and MaxDiffInterval = 1 > weeks. But how can I trigger it? > -- Jörg Steffens [email protected] Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- 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.
