>Tell them to turn on TCP Keepalives on both sides (Linux its a
>syssctl(8), WinNT by hacking random registry entries and setting them to
>arbitrary and random values)
>
>Up the TCP state expiration timeout values on any stateful L2/L3 devices
>en route.
Not buying that, the default for Linux a
On 9/29/2010 3:00 AM, Henrik Johansen wrote:
> 'Joseph L. Casale' wrote:
>> I have several physical and virtual fd's that are just unreliable to backup
>> against two sd/dir's all at 5.0.3 running CentOS5x64.
>>
>> Anyone else having these issues? I get random network IO failures as
>> suggested by
On Martes 28 Septiembre 2010 20:19:25 Joseph L. Casale escribió:
> Things were working well until recently so I am pretty sure an update to
> the OS has probably caused this by breaking something for the FD software.
> None of the similar hardware running Win2003 is affected.
>
Do you have a WSU
'Joseph L. Casale' wrote:
>I have several physical and virtual fd's that are just unreliable to backup
>against two sd/dir's all at 5.0.3 running CentOS5x64.
>
>Anyone else having these issues? I get random network IO failures as
>suggested by the dir?
We are seeing the same pattern - W28K boxes f
>I'm curious if you have solved the issue or if you still have it. Also are
>you running Symantec products?
Hey guys, keep the reply's on list for the benefit of the community. This
thread is a
prime example of other effected users.
Heavens no, I think even the proxy blocks Symantec, just to s
>I have seen this several times. Particularly with slow laptop clients
>and compression turned on. Some NIC drivers appear to shutoff power to
>the network interface after a period of network inactivity, and I
>believe the inactivity is probably due to the laptop being too
>underpowered to comp
I have several physical and virtual fd's that are just unreliable to backup
against two sd/dir's all at 5.0.3 running CentOS5x64.
Anyone else having these issues? I get random network IO failures as
suggested by the dir?
Thanks,
jlc
---
