Hello Matthias,

While we attempt to fully support older FDs, in your case, your FD is four years older than the Director.  I would suggest that this is not an ideal combination -- i.e. I recommend that you upgrade your FD, and if you still have problems, report it again.   I suspect that the connection was probably dropped because you do not have Heartbeat Interval set on the FD and it waited a very long time for the Director.  If I am not mistaken, by default the heartbeat interval is turned on in newer FDs.  At least that would be something to check.

Best regards,

Kern

I have managed to keep a long backup running (125GB /23 hours). While
the remote FD reports a success

 JobId  Level    Files      Bytes   Status   Finished        Name
======================================================================
   940  Full   1,022,421    125.2 G  OK       20-Jun-17 15:01 backup


the director reports a failure:


Standard-Device Elapsed time=23:34:45, Transfer rate=1.478 M Bytes/second
 Sending spooled attrs to the Director. Despooling 355,532,878
fafnir Fatal error: Network error with FD during Backup: ERR=Connection
reset by peer
fafnir Fatal error: No Job status returned from FD.

Error: Bacula fafnir 7.4.2 (06Jun16):
  Build OS:               x86_64-unknown-openbsd6.0 openbsd 6.0
  JobId:                  940
  Job:                    backup.2017-06-19_15.26.55_07
  Backup Level:           Full
  Client:                 "<client>" 5.2.6 (21Feb12)
x86_64-pc-linux-gnu,debian,7.0
  FileSet:                "Unixoid" 2017-03-29 23:05:01
  Pool:                   "Standard" (From Command input)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "Standard-Device" (From command line)
  Scheduled time:         19-Jun-2017 15:26:50
  Start time:             19-Jun-2017 15:26:58
  End time:               20-Jun-2017 18:57:39
  Elapsed time:           1 day 3 hours 30 mins 41 secs
  Priority:               10
  FD Files Written:       0
  SD Files Written:       1,022,421
  FD Bytes Written:       0 (0 B)
  SD Bytes Written:       125,469,539,182 (125.4 GB)
  Rate:                   0.0 KB/s
  Software Compression:   None
  Snapshot/VSS:           no
  Encryption:             no
  Accurate:               no
  Volume name(s):         FVol-0002|FVol-0005|FVol-0001|FVol-0006
  Volume Session Id:      40
  Volume Session Time:    1497446317
  Last Volume Bytes:      40,602,488,821 (40.60 GB)
  Non-fatal FD errors:    1
  SD Errors:              0
  FD termination status:  Error
  SD termination status:  OK
  Termination:            *** Backup Error ***


I noticed that the director still considered the job "running" while the
FD had already reported it as finished. The db backend seemed to be
quite busy for about an hour. The last message I got from the director was

 Sending spooled attrs to the Director. Despooling 355,532,878


until finally the error message appeared.

Matthias

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users