or you can split the backup in smaller jobs. Try to figure out a stable "window" when the connection is ok and then run there a smaller backup job (i.e. only a few folders). Repeat this until all the folders are covered by the backup jobs.
vineri, 10 februarie 2017, 19:33:44 UTC+2, Stephan Duehr a scris: > Hi, > > did you set heartbeat interval = 60 in the Director, Client and Storage > resource? > > If some dynamic IP connection is involved and you are hit by an IP change > while > the backup runs, there's not much that Bareos can do about. If that's the > case, > using openvpn could help, as Bruno said. > > Regards > > Stephan > > On 02/10/2017 12:24 PM, mark8264 wrote: > > hi, > > > > i have to backup a lot of data on a server being at another location, but > > the network connection between bareos server and the target one is not > > always stable. > > > > Therefore i get following error on client-side during backup: > > Error: lib/bsock_tcp.c:405 Write error sending -1 bytes to client:xxx:9102: > > ERR=Input/output error > > Fatal error: filed/backup.c:1257 Network send error to SD. ERR=Input/output > > error > > Error: lib/bsock_tcp.c:434 Socket has errors=1 on call to client:xxx:9102 > > Error: lib/bsock_tcp.c:405 Write error sending 108 bytes to > > client:xxx:9102: ERR=Input/output error > > > > server-side: > > 9-Feb 03:55 bareos-dir JobId 155: Fatal error: Network error with FD during > > Backup: ERR=Die Wartezeit für die Verbindung ist abgelaufen > > 09-Feb 03:55 bareos-dir JobId 155: Error: Director's comm line to SD > > dropped. > > 09-Feb 03:55 bareos-dir JobId 155: Fatal error: No Job status returned from > > FD. > > 09-Feb 03:55 bareos-dir JobId 155: Error: Bareos bareos-dir 16.2.4 > > (01Jul16): > > Build OS: x86_64-redhat-linux-gnu redhat CentOS Linux > > release 7.0.1406 (Core) > > JobId: 155 > > Job: xxx > > Backup Level: Full > > Client: "xxx" 16.2.4 (01Jul16) Microsoft Windows Server > > 2012 Standard Edition (build 9200), 64-bit,Cross-compile,Win64 > > FileSet: xxx > > Pool: "monthly" (From Run Pool override) > > Catalog: "MyCatalog" (From Client resource) > > Storage: "File" (From Job resource) > > Scheduled time: 09-Feb-2017 03:00:00 > > Start time: 09-Feb-2017 03:00:02 > > End time: 09-Feb-2017 03:55:11 > > Elapsed time: 55 mins 9 secs > > Priority: 10 > > FD Files Written: 0 > > SD Files Written: 0 > > FD Bytes Written: 0 (0 B) > > SD Bytes Written: 33,831,269 (33.83 MB) > > Rate: 0.0 KB/s > > Software Compression: None > > VSS: no > > Encryption: no > > Accurate: no > > Volume name(s): xxx > > Volume Session Id: 18 > > Volume Session Time: 1486463671 > > Last Volume Bytes: 18,901,110,770 (18.90 GB) > > Non-fatal FD errors: 2 > > SD Errors: 0 > > FD termination status: Error > > SD termination status: Error > > Termination: *** Backup Error *** > > > > it is not always on same position. I also set the heartbeat intervall to 60 > > seconds. > > > > I know the job could be finished successfully, because i have started it > > manually and it didn't aborted. > > > > > > Is there a way to solve my problem? > > > > kind regards > > > > > -- > Stephan Dühr [email protected] > Bareos GmbH & Co. KG Phone: +49 221-630693-90 > http://www.bareos.com > > 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. Steffens, Philipp 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.
