Hi, On 3/23/2007 10:35 PM, Michael Proto wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jason King wrote: >> I have my director in one city and another server with an attached tape >> drive in another city. The server in the remote city is running the SD >> and the FD...the director initiates and handles the job. The job will >> start, but will end prematurely after it backs up about 4 GB of data. >> These are the error messages I'm getting: >> >> 23-Mar 10:28 dctn-fd: dctn.2007-03-23_09.25.48 Fatal error: >> ../../filed/backup.c:873 Network send error to SD. ERR=Input/output error >> 23-Mar 10:28 dctn-fd: dctn.2007-03-23_09.25.48 Error: >> ../../lib/bnet.c:406 Write error sending len to Storage >> daemon:dctn.informs.com:9103: ERR=Input/output error >> >> I can find NO instance of these messages on the internet. I have no idea >> what they mean. I mean, what the heck is a "len" that is being sent to >> the storage daemon, and why all of a sudden can the storage daemon not >> write. What is causing this network error? >> >> GAH!!!! >> >> Any assistance would be appreciated. >> > > Jason, > > Are you aware of any network interruptions that might be affecting your > backups?
Note that network interruptions because intermediate routers or firewalls drop idle TCP connections after a while will affect your backups. You can use a heartbeat to prevent problems. Anyway, this is not what I think is happening. > I seem to remember this sort of error occurring when the TCP > connection from the fd on the client to the sd on the storage server is > severed. Since the backup all occurs over a single TCP session, an > interruption of that session will cause this error. I haven't seen it in > a few months but I remember this sort of thing used to cause me tons of > headaches when backing-up large (disk-wise) servers. The above problem seems to be local to the FD-SD-connection. If you're using spooling, the connection might be idle for a long time while despooling, or the connection might be idle while the FD is busy. In both cases, some network device could timeout the connection. Try using the heartbeat interval settings, and verify your network equipment doesn't misbehave. Arno > > - -Proto > > - -- > Michael Proto | SecureWorks > Unix Administrator | > PGP ID: 5D575BBE | [EMAIL PROTECTED] > ******************************************************* > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (FreeBSD) > > iD8DBQFGBEgJOLq/wl1XW74RAnJ9AKCBCPd4WsEuNcisL8zoBMe5abykSQCfVxir > 75RgKaY+DaDWTHDoc5tYerQ= > =zsA4 > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
