On 8/6/2015 5:09 AM, Raimund Sacherer wrote:
>
>> And finally, many switches also have TCP timeout settings and/or EEE and
>> power management that could potentially not work correctly with either
>> the FreeBSD or the Windows network stacks.
> That sound's interesting, I saw a couple of posts talking about a keepalives, 
> I will configure our FD's, SD's an the director for a 300 seconds timeout and 
> we will see if we still get those errors.
>
> Maybe it has nothing to do with the switch to FreeBSD, because at nearly the 
> same time we migrated our servers from physical servers to VMWare, maybe it's 
> the virtual vmware switch which makes troubles.
>
> Well, in either case, i'l see how it goes with the keep alive configured,

Fyi, version 7.x of the client daemon added progress data. The FD sends 
progress data to the Dir every 30 seconds. In version 5.x the Dir - FD 
connection sat idle during a backup. If your Windows FDs are 5.x then 
that could explain why they fail on the same network where the other FDs 
do not.


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