Bacula-users

Re: [Bacula-users] Fatal error: Network error with FD during Backup: ERR=Connection timed out

2010-01-16 04:22:01
Subject: Re: [Bacula-users] Fatal error: Network error with FD during Backup: ERR=Connection timed out
From: Carlo Filippetto <carlo.filippetto AT gmail DOT com>
To: Josh Fisher <jfisher AT pvct DOT com>
Date: Sat, 16 Jan 2010 10:18:41 +0100
Sorry, there's a misunderstanding..
I'm far 600km from the server, while all the server are in the same server farm!

I have upgraded the driver of the NIC and grow up to 45 minute the
hearthbeat, now it goes well

Thank's a lot

CIAO,
Carlo



2010/1/15 Josh Fisher <jfisher AT pvct DOT com>:
>
> Carlo Filippetto wrote:
>>
>> I tried disabling any power saving features.. but the backup faild!!
>> I haven't any othe nic card (the server is 600km away) and I can't do
>> nothig manually..
>> The driver is ok
>>
>> Now??
>> what can I tried??
>>
>>
>
> Bacula requires the SD-FD connection stay up throughout the backup. If it is
> dropped for any reason, then you will see this error. Since the server is
> 600km away, that could be difficult. One solution might be to run SD locally
> and backup to local storage, then rsync backup volumes to the remote server.
>
>>
>> 2010/1/13 Josh Fisher <jfisher AT pvct DOT com>:
>>
>>>
>>> Carlo Filippetto wrote:
>>>
>>>>
>>>> Hi all,
>>>> I have a problem when backup windows 2008 64 bit, with Exchange 2007
>>>> (bacula 3.0.3 on Centos 5.3)
>>>>
>>>> On google I found and insert
>>>>     Heartbeat Interval = 1 minutes
>>>>
>>>> on both client and server, but only one time the full backup goes well,
>>>> after all the other faild with the erro in the title
>>>>
>>>> What can I do?
>>>>
>>>>
>>>
>>> I have had this problem before. It has always been related to the NIC or
>>> NIC
>>> driver in the client machine. Years ago this happened with the NIC built
>>> into the NFS4 Nvidia chipset and was fixed by a driver update from
>>> Nvidia.
>>> In a Lenovo laptop I believe power saving modes in the Windows NIC driver
>>> may have caused this. If the client doesn't transmit for a while because
>>> it
>>> is busy with compression or building a VSS snapshot then the driver may
>>> turn
>>> off the power to the NIC transmitter. That is just a guess, but a USB
>>> external NIC worked perfectly in the same machine. Start with disabling
>>> any
>>> power saving features of the NIC in the Windows machine. Try another NIC
>>> if
>>> possible. See if there is an updated NIC driver available.
>>>
>>>
>>>>
>>>> Grazie, ciao
>>>>
>>>> Carlo
>>>>
>>>>
>

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users