> Stephan Heine - [Genetic Interactive] wrote:
> > Hi,
> > On Tuesday 28 June 2005 10:49 Arno Lehmann
> > wrote:
> >>Now, unfortunately the debug output has no timestamps, but the only
> >>thing I can imagine is that the SD needs some time in between and the FD
> >>or some router in between then times out the connection.
> >>Have you tried the Heratbeat interval setting?
> > I have tried it now (Heartbeat Interval = 5 seconds as well as Heartbeat
> > Interval = 5 minutes),
> > it unfortunately it did not make a difference.
> > I also had a look at the status of the client FD while the backup is
> > running,
> > and the following was peculiar:
> > 1. Although it is a 100MB FullDuplex auto negotiating NIC the speed is
> > +/-100k/sec and then the bytes/sec bleeds off until the job dies.
> > On a standard NIC (built into the same system) it moves like a rocket.
> > Should I send another trace with the Heartbeat Interval Setting enabled
> not for me at least... I'd say this is a good indication that the
> problem is not baculas and therefore the bacula debug output will not
> More helpful might be to search support for the nvidia network drivers
> or hardware, I guess...
20 points to you. It was drivers that caused my problems. Here is the
OS: Windows XP Pro
Mainboard: Epox EP-9NDA3J
Chipset: NVidia NForce 3
Ethernet Driver Editions with Issues:
The NForce 3's download does not include the latest drivers and
does not seem to be updated.
So as per test, I tried the NForce4's ethernet drivers.
Drivers that worked:
Backup running, me smiling.
Tel: +27 861 99 88 99
Fax: +27 861 99 77 99
Cell: +27 82 467 1164