Bacula-users

Re: [Bacula-users] FD Errors on Win2003

2009-01-10 07:46:33
Subject: Re: [Bacula-users] FD Errors on Win2003
From: Kevin Keane <subscription AT kkeane DOT com>
Date: Sat, 10 Jan 2009 04:34:08 -0800
Bruno Friedmann wrote:
> Gabriele Bulfon wrote:
>   
>> Hello,
>> I'm having trouble with a win2003 client running the agent.
>> >From time to time only that client stops the backup with the following 
>> >error:
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: Network error with FD during Backup: ERR=Connection reset by 
>> peer
>> 09-Jan 03:03 smartlink-sd: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: append.c:159 Error reading data header from FD. ERR=Connection 
>> reset by peer
>> 09-Jan 03:03 smartlink-sd: Job write elapsed time = 01:34:39, Transfer rate 
>> = 9.796 M bytes/second
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Fatal error: No Job status returned from FD.
>> 09-Jan 03:03 smartlink-dir: Enterprise_Backup_OFFICE.2009-01-08_21.50.00 
>> Error: Bacula smartlink-dir 2.2.2 (06Aug07): 09-Jan-2009 03:03:35
>>   Build OS:               i386-pc-solaris2.10 solaris 5.10
>>   JobId:                  858
>>   Job:                    Enterprise_Backup_OFFICE.2009-01-08_21.50.00
>>   Backup Level:           Full
>>   Client:                 "office-fd" Windows Server 2003,MVS,NT 5.2.3790
>>   FileSet:                "officeFileSet" 2008-12-22 21:50:00
>>   Pool:                   "ThursdayPool" (From Run pool override)
>>   Storage:                "QUANTUM" (From Job resource)
>>   Scheduled time:         08-Jan-2009 21:50:00
>>   Start time:             09-Jan-2009 01:28:52
>>   End time:               09-Jan-2009 03:03:35
>>   Elapsed time:           1 hour 34 mins 43 secs
>>   Priority:               10
>>   FD Files Written:       0
>>   SD Files Written:       71,801
>>   FD Bytes Written:       0 (0 B)
>>   SD Bytes Written:       55,635,942,980 (55.63 GB)
>>   Rate:                   0.0 KB/s
>>   Software Compression:   None
>>   VSS:                    no
>>   Encryption:             no
>>   Volume name(s):         GIOVEDI2
>>   Volume Session Id:      4
>>   Volume Session Time:    1231408365
>>   Last Volume Bytes:      246,756,142,080 (246.7 GB)
>>   Non-fatal FD errors:    0
>>   SD Errors:              0
>>   FD termination status:  Error
>>   SD termination status:  Error
>>   Termination:            *** Backup Error ***
>> As you can see, the machine was backed up for almost 1 hour and half.
>> This happened 10-12 times in the last few months.
>> I already investigated any possible network problem or anything out of 
>> Bacula happening during the night (when backup runs). There doesn't seem to 
>> be any other problem.
>> What may be the cause?
>> thanx for any help.
>> Gabriele.
>>
>>
>>     
> Dear Gabriele, on one site of my customers, we encounter hard time with one 
> windows server.
> It has work nicely during 10 month. And suddently make lot's of error with 
> the bacula server.
> like yours.
>
> It's twin other server doesn't have any trouble.
> It's start happening after a big update on hardware (firmware) and software 
> from hp ( note that both server was updated at the
> same time )
>
> I've run long ping test between server, and what was comic is that during 
> some days it work with a 0% packet loss other days
> this was around 25% ...
>
> Later we reboot all network component, swithches, hubs, routers : and 
> everything goes nicely.
> Why : continue to be a mystery for me. But the result is here.
> >From that reboot time, we don't see any trouble.
>   
You may want to check out the Ethernet wiring: cable quality, cable 
lengths, any kinks or breaks in the cables, ...

At one of my customers, a couple of computers show very similar 
problems. Some days, they would run fast, other days they'd crawl. Are 
you by any chance using a managed hub? If so, you may want to log on to 
the hub and see if it can test the cables.

At my customers, it turned out that the Ethernet cables were just 
marginal. The managed hub actually showed the problem: those computers 
that worked well showed a definite cable length, usually between 30 and 
50 feet. Those that were marginal showed "undetermined cable length". I 
haven't tracked all of them down yet, but in at least one case, a large 
part of the problem that the Ethernet cable from the wall port to the 
workstation was extremely long and coiled up under the desk. I suspect 
that the cable quality also was pretty poor, and the cable was kinked in 
a few places. Some strands may well have broken, too. I only just 
replaced the cable yesterday, so it's too early to tell if it fixed the 
problem.

-- 
Kevin Keane
Owner
The NetTech
Turn your NetWORRY into a NetWORK!

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>