Bacula-users

Re: [Bacula-users] bacula - backup.c:892 Network send error

2013-01-29 11:25:35
Subject: Re: [Bacula-users] bacula - backup.c:892 Network send error
From: "Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC]" <uthra.r.rao AT nasa DOT gov>
To: "lst_hoe02 AT kwsoft DOT de" <lst_hoe02 AT kwsoft DOT de>, "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Tue, 29 Jan 2013 10:22:19 -0600
As far as replacing the NIC on the bacula server - The backups were running 
fine all these days. I have run several Full and incremental backups of these 
two clients in the past.  I am not sure why I am suddenly having a problem? 
Last evening I tried to run a Full backup of one of the client again and this 
morning I saw the job was hung and the client machine had to be power cycled to 
bring it back on-line.

On my bacula backup server (RHEL6) . I have set-up "Heartbeat interval=120" on 
the server in the bacula-dir.conf, bacula-fd.conf and bacula-sd.conf and 
bconsole.conf configuration files. Should I add Heartbeat Interval to the 
client config file also client-dir and client-fd??

I am even thinking to try replace the network cable on the bacula server?

If you have any comments or suggestion please let meknow.

Thank you.
Uthra



-----Original Message-----
From: lst_hoe02 AT kwsoft DOT de [mailto:lst_hoe02 AT kwsoft DOT de] 
Sent: Friday, January 25, 2013 3:31 PM
To: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] bacula - backup.c:892 Network send error


Zitat von "Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC]"  
<uthra.r.rao AT nasa DOT gov>:

> Thank you for your reply. Backup of these clients have been running 
> fine all these days. Only when I started a FULL back-up this week of 
> the two clients they failed:
>
> Client1:
> JobId 4183: Fatal error: backup.c:892 Network send error to SD.  
> ERR=Broken pipe 24-Jan 20:23
>
> Client2:
> JobId 4180: Fatal error: backup.c:892 Network send error to SD.  
> ERR=Broken pipe 24-Jan 13:16 ldy-sd JobId 4180: Fatal error:  
> spool.c:301 Fatal append error on device "Drive-1" (/dev/nst0):  
> ERR=block.c:1045 Read error on fd=5 at file:blk 0:0 on device 
> "Drive-1" (/dev/nst0). ERR=Input/output error.
>
> Uthra

As said we also had this kind of problems. On Machine with ~20G failed only 
from time to time but always at Full. The other machine failed all Full to tape 
after some random amount of data ranging from 300G to 1.6T from around 1.8T. 
After replacing the NIC at the bacula server the problem went away. Before this 
we have tested all sort of other network related things to no avail, so it 
might also be the problem you are facing.

Regards

Andreas



------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, 
Windows 8 Apps, JavaScript and much more. Keep your skills current with 
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. 
ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
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>