okay, i guess i found the solution the other hardware network adapter maybe reacts different than the old one (thats my assumption)
at least using the info from this link helped me to fix the issue: http://wiki.bacula.org/doku.php?id=faq#my_backup_starts_but_dies_after_a_while_with_connection_reset_by_peer_error i quote: ------ # netstat -to tcp 0 0 client:9102 server:54043 ESTABLISHED keepalive (7196.36/0/0) tcp 0 0 client:43628 server:9103 ESTABLISHED keepalive (7197.26/0/0) In that case you can try setting the system defaults to lower value, for example on GNU/Linux systems (or check URLs above for other systems) with: sysctl -w net.ipv4.tcp_keepalive_time=60 Put that in /etc/sysctl.conf or /etc/sysctl.d/* to keep it across reboots. ------ i did this sysctl setup on the baculaserver which is virtualized inside a vmware and it helped to solve the problem, i could tweak the time of course but its now the last day before christmas and already 4.30 pm work time over and so i dont care :D have a nice holiday all of you bye +---------------------------------------------------------------------- |This was sent by adam.b.sz...@ericsson.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
